summaryrefslogtreecommitdiffstats
path: root/tests/basic
diff options
context:
space:
mode:
authorAmar Tumballi <amarts@redhat.com>2019-05-21 11:20:01 +0530
committerAmar Tumballi <amarts@redhat.com>2019-05-21 11:41:43 +0000
commit72a83c71cc506e3a4d775b622717052c93f5242f (patch)
tree626272eeb7cc0a07a037c01d765e853df851491f /tests/basic
parentc8ba4c5f6f0bac4f9bdc7d6dec217deecbeb717a (diff)
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 <amarts@redhat.com>
Diffstat (limited to 'tests/basic')
-rw-r--r--tests/basic/quick-read-with-upcall.t6
1 files changed, 5 insertions, 1 deletions
diff --git a/tests/basic/quick-read-with-upcall.t b/tests/basic/quick-read-with-upcall.t
index 951faee..4e5df25 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