run-tests: allow some slack about 'waiting on lock' message
It is common to run the tests on very loaded machine when concurrent run might take a bit longer. Such message are usually harmless, but anoying as they break the tests. Test that explicitly depends on this value have been adjusted. This make them more robust anyway. A fun case was `test-clone-pull-corruption.t` which, without the previous changeset introducing extra flushing, ended use having a line 31 (`pulling from ../source`) changing order because the warning message was no longer flushing stdin before using stderr (stderr being invisible in the test). Differential Revision: https://phab.mercurial-scm.org/D9507
Showing
- tests/run-tests.py 1 addition, 0 deletionstests/run-tests.py
- tests/test-basic.t 1 addition, 0 deletionstests/test-basic.t
- tests/test-commandserver.t 2 additions, 0 deletionstests/test-commandserver.t
- tests/test-lock-badness.t 1 addition, 1 deletiontests/test-lock-badness.t
- tests/test-phases-exchange.t 1 addition, 1 deletiontests/test-phases-exchange.t
Loading
Please register or sign in to comment