Mercurial > evolve
comparison tests/test-prev-next.t @ 4395:610999a1bae1 stable
test: wider time matching in prev/next lock testing
There does not seems to be a reasons for specifically matching 4-6 seconds.
Wider matching will avoid intermittent failure.
| author | Pierre-Yves David <pierre-yves.david@octobus.net> |
|---|---|
| date | Fri, 08 Feb 2019 09:26:48 +0100 |
| parents | 8974a05a49fa |
| children | 83d45ded5af8 d2c1e6d61658 |
comparison
equal
deleted
inserted
replaced
| 4388:20d1ceef2df2 | 4395:610999a1bae1 |
|---|---|
| 337 | 337 |
| 338 $ hg amend --edit & | 338 $ hg amend --edit & |
| 339 $ sleep 1 | 339 $ sleep 1 |
| 340 $ hg prev | 340 $ hg prev |
| 341 waiting for lock on working directory of $TESTTMP/repo held by process '*' on host '*' (glob) | 341 waiting for lock on working directory of $TESTTMP/repo held by process '*' on host '*' (glob) |
| 342 got lock after [4-6] seconds (re) | 342 got lock after (\d+) seconds (re) |
| 343 1 files updated, 0 files merged, 0 files removed, 0 files unresolved | 343 1 files updated, 0 files merged, 0 files removed, 0 files unresolved |
| 344 [0] one | 344 [0] one |
| 345 $ wait | 345 $ wait |
| 346 | 346 |
| 347 $ hg amend --edit & | 347 $ hg amend --edit & |