-
Notifications
You must be signed in to change notification settings - Fork 37.7k
Test framework: only cleanup on successful test runs #8095
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ACK |
ACK 64fc92f |
Concept ACK. Wouldn't it make sense to also Tailing the debug.log from rpc_tests.py makes sense, but would at least require #8098. |
utACK 64fc92f |
@arowser why are you asking the same question in so many random PRs? This is disruptive or development and annoying. Please, stop. |
64fc92f
to
1ad9339
Compare
@MarcoFalke Updated with the print statement as suggested. |
utACK 1ad9339 |
ACK 1ad9339 |
1ad9339 Test framework: only cleanup on successful test runs (Suhas Daftuar)
1ad9339 Test framework: only cleanup on successful test runs (Suhas Daftuar)
Core QA cherries bitcoin/bitcoin#8047 - [qa] test_framework: Set wait-timeout for bitcoind procs bitcoin/bitcoin#8095 - Test framework: only cleanup on successful test runs bitcoin/bitcoin#8214 - [qa] mininode: fail on send_message instead of silent return
Don't cleanup the datadir's on test failure.
I hope that this should make it easier to debug rare-failing tests, as we'll at least have the debug.log's available to go through.
@MarcoFalke: After this, we could perhaps add to the
rpc-tests.py
script some functionality to tail the last few hundred lines of debug.log for each node if a test fails, so that if a job fails in travis, we'll have more info to look at?