tests: correct the output order about starting a background thread for Windows
I didn't track down where this change occurred. I assume it's related to some buffering changes, and/or an explicit flush somewhere. Differential Revision: https://phab.mercurial-scm.org/D9539
Showing
- tests/test-copy-move-merge.t 1 addition, 1 deletiontests/test-copy-move-merge.t
- tests/test-double-merge.t 1 addition, 1 deletiontests/test-double-merge.t
- tests/test-graft.t 1 addition, 1 deletiontests/test-graft.t
- tests/test-issue672.t 2 additions, 2 deletionstests/test-issue672.t
- tests/test-merge-commit.t 2 additions, 2 deletionstests/test-merge-commit.t
- tests/test-merge7.t 1 addition, 1 deletiontests/test-merge7.t
- tests/test-rename-merge1.t 1 addition, 1 deletiontests/test-rename-merge1.t
- tests/test-rename-merge2.t 14 additions, 16 deletionstests/test-rename-merge2.t
- tests/test-subrepo.t 1 addition, 1 deletiontests/test-subrepo.t
- tests/test-up-local-change.t 1 addition, 1 deletiontests/test-up-local-change.t
Loading
Please register or sign in to comment