It's overly noisy, and not useful to have the bitcoin nodes log to stdout in the functional tests. In case of troubleshooting the debug.log files can be inspected.
This was the behavior before #13004.
test: Don't log to stdout in functional tests #13071
pull laanwj wants to merge 1 commits into bitcoin:master from laanwj:2018_04_test_output changing 1 files +1 −0-
laanwj commented at 9:52 AM on April 25, 2018: member
-
3b0e58ecae
test: Don't log to stdout in functional tests
It's overly noisy, and not useful to have the bitcoin nodes log to stdout in the functional tests. In case of troubleshooting the `debug.log` files can be inspected. This was the behavior before #13004.
- laanwj added the label Tests on Apr 25, 2018
-
laanwj commented at 12:26 PM on April 25, 2018: member
Strange - I can't reproduce the problem here, and don't know what fixed it here either as
logtoconsoleoption doesn't exist. - laanwj closed this on Apr 25, 2018
-
MarcoFalke commented at 12:40 PM on April 25, 2018: member
Hmm, shouldn't daemon default to true for bitcoind, and thus it shouldn't log to the console?
-
laanwj commented at 1:17 PM on April 25, 2018: member
Hmm, shouldn't daemon default to true for bitcoind, and thus it shouldn't log to the console?
I don't think the functional tests use -daemon. They do pass
-noprinttoconsolethough so I have no clue why I had this issue. - MarcoFalke locked this on Sep 8, 2021
Contributors
Labels