Mercurial > evolve
changeset 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 | 20d1ceef2df2 |
children | 83d45ded5af8 d2c1e6d61658 |
files | tests/test-prev-next.t |
diffstat | 1 files changed, 1 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/tests/test-prev-next.t Thu Jan 31 15:38:48 2019 +0530 +++ b/tests/test-prev-next.t Fri Feb 08 09:26:48 2019 +0100 @@ -339,7 +339,7 @@ $ sleep 1 $ hg prev waiting for lock on working directory of $TESTTMP/repo held by process '*' on host '*' (glob) - got lock after [4-6] seconds (re) + got lock after (\d+) seconds (re) 1 files updated, 0 files merged, 0 files removed, 0 files unresolved [0] one $ wait