test: wider another 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.
--- a/tests/test-prev-next.t Fri Feb 08 09:26:48 2019 +0100
+++ b/tests/test-prev-next.t Fri Feb 08 10:21:09 2019 +0100
@@ -349,7 +349,7 @@
$ hg next --evolve
waiting for lock on working directory of $TESTTMP/repo held by process '*' on host '*' (glob)
1 new orphan changesets
- got lock after [4-6] seconds (re)
+ got lock after (\d+) seconds (re)
move:[2] two
atop:[3] one
working directory now at a7d885c75614