Make sure important messages aren't thrown away.
- Log messages with type>QtDebugMsg as non-debug
- Change serious messages from qDebug to qWarning
Keep just-for-info messages at qDebug, those can still be activated with -debug=qt.
qt: Always log warning/error messages to debug.log #4448
pull laanwj wants to merge 2 commits into bitcoin:master from laanwj:2014_07_qt_payment_rq_logging changing 6 files +36 −36-
laanwj commented at 1:25 PM on July 1, 2014: member
-
d95ba75825
qt: Log messages with type>QtDebugMsg as non-debug
More important messages should end up in the log no matter if -debug=qt is set.
-
33fdd99288
qt: Change serious messages from qDebug to qWarning
By changing the logging stream for warnings from qDebug to qWarning, these will always be logged to debug.log.
-
BitcoinPullTester commented at 1:42 PM on July 1, 2014: none
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/p4448_33fdd99288fd257d6b5a3797a0a68aff649a3a71/ for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
-
gavinandresen commented at 2:25 PM on July 1, 2014: contributor
Nice.
- gavinandresen referenced this in commit f04f123407 on Jul 1, 2014
- gavinandresen merged this on Jul 1, 2014
- gavinandresen closed this on Jul 1, 2014
- MarcoFalke locked this on Sep 8, 2021
Contributors