tests: Spurious failure in bug-1117851.t
This test runs file renames in a loop in the background and expects them to be done within 75 seconds. On slower VMs the operation takes about 75-80 seconds to complete causing the test to fail randomly. Increased the timeout to 120 seconds. Change-Id: I103e630c5a1bcea1fb4c7842892a2e67714c3fbb BUG: 1163543 Signed-off-by: Nithya Balachandran <nbalacha@redhat.com> Reviewed-on: http://review.gluster.org/10111 Reviewed-by: Jeff Darcy <jdarcy@redhat.com> Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
This commit is contained in:
parent
f66a85a484
commit
614dbff79f
@ -80,10 +80,10 @@ TEST move_files $M1
|
||||
# It's regrettable that renaming 1000 files might take more than 30 seconds,
|
||||
# but on our test systems sometimes it does, so double the time from what we'd
|
||||
# use otherwise. There still seem to be some spurious failures, 1 in 20 when
|
||||
# this does not complete, added an additional 15 seconds to take false reports
|
||||
# out of the system, during test runs.
|
||||
EXPECT_WITHIN 75 "done" cat $M0/status_0
|
||||
EXPECT_WITHIN 75 "done" cat $M1/status_1
|
||||
# this does not complete, added an additional 60 seconds to take false reports
|
||||
# out of the system, during test runs, especially on slower test systems.
|
||||
EXPECT_WITHIN 120 "done" cat $M0/status_0
|
||||
EXPECT_WITHIN 120 "done" cat $M1/status_1
|
||||
|
||||
TEST umount $M0
|
||||
TEST umount $M1
|
||||
|
Loading…
x
Reference in New Issue
Block a user