From 72a83c71cc506e3a4d775b622717052c93f5242f Mon Sep 17 00:00:00 2001 From: Amar Tumballi Date: Tue, 21 May 2019 11:20:01 +0530 Subject: tests/quick-read-with-upcall.t: increase the timeout Running with 2 second sleep at this place caused failures like: `not ok 14 [ 2014/ 7] < 41> 'test-message1 cat /mnt/glusterfs/1/test.txt' -> 'Got "test-message0" instead of "test-message1"'` in few runs in 100 iterations. But when increased to higher than sleep 3, have not seen any failures in 100 runs. While I don't know the exact reasons for the behavior yet, looks like this increase in wait helps to pass the regression without failures. updates: bz#1693692 Change-Id: I0610b79bea53e36de3eea6c11234b7fc9dfd6232 Signed-off-by: Amar Tumballi --- tests/basic/quick-read-with-upcall.t | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'tests/basic') diff --git a/tests/basic/quick-read-with-upcall.t b/tests/basic/quick-read-with-upcall.t index 951faee02cc..4e5df25c65e 100644 --- a/tests/basic/quick-read-with-upcall.t +++ b/tests/basic/quick-read-with-upcall.t @@ -37,7 +37,11 @@ TEST write_to "$M0/test.txt" "$D1" EXPECT "$D1" cat $M0/test.txt EXPECT "$D0" cat $M1/test.txt -sleep 2 +# This is 3.7 for no good reason. We could have kept this to +# any number above 2 seconds. Noticed that when it is 2 seconds, or +# less, there is a possibility of not getting a lookup on the same inode. +sleep 3.7 + EXPECT "$D1" cat $M1/test.txt TEST $CLI volume set $V0 features.cache-invalidation on -- cgit