# HG changeset patch
# User Pierre-Yves David <pierre-yves.david@octobus.net>
# Date 1549614408 -3600
# Node ID 610999a1bae1fcb17f9fc535f3cddacc1120c32e
# Parent  20d1ceef2df24399bef9fdab793d1298441ee03f
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.

diff -r 20d1ceef2df2 -r 610999a1bae1 tests/test-prev-next.t
--- 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