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
qa: Note on test order in test_runner #11965
Conversation
faaa4d3
to
fa2333f
Compare
ACK fa2333f. Nit, should new tests be added at the end of the run-time section or should there be an effort to keep them sorted? |
I would clarify it a little more, e.g.
or maybe 'line' instead of 'comment'. |
fa2333f
to
fadf60e
Compare
@promag Adding at the end of run-time sections doesn't help with merge conflict. Sorting by name would. Though, since we plan to rename the tests, I don't want to go in this direction. |
utACK fadf60e |
fadf60e qa: Note on test order in test_runner (MarcoFalke) Pull request description: C.f. bitcoin#11964 Tree-SHA512: 5f087965093722d9e7a3febddcc187e412bd0636a7ed2da60111668fe3bba6668110e25a38ddcccc0d0aae132611c56fa72f3f0c473fb3fb59e38be445edfcd5
fadf60e qa: Note on test order in test_runner (MarcoFalke) Pull request description: C.f. bitcoin#11964 Tree-SHA512: 5f087965093722d9e7a3febddcc187e412bd0636a7ed2da60111668fe3bba6668110e25a38ddcccc0d0aae132611c56fa72f3f0c473fb3fb59e38be445edfcd5
C.f. #11964