From 988e00f83cb74c908471caf6af9cbce05b7f95c9 Mon Sep 17 00:00:00 2001 From: Atin Mukherjee Date: Sat, 9 May 2015 12:23:10 +0530 Subject: tests: fix bitrot spurious failures Change-Id: I55bd62480b7ee38cf7b29aeba67b19b0c5bbe2fb BUG: 1220016 Signed-off-by: Atin Mukherjee Reviewed-on: http://review.gluster.org/10702 Reviewed-by: Pranith Kumar Karampuri Tested-by: Vijay Bellur --- .../bugs/bitrot/1209752-volume-status-should-show-bitrot-scrub-info.t | 3 +++ 1 file changed, 3 insertions(+) (limited to 'tests/bugs/bitrot/1209752-volume-status-should-show-bitrot-scrub-info.t') diff --git a/tests/bugs/bitrot/1209752-volume-status-should-show-bitrot-scrub-info.t b/tests/bugs/bitrot/1209752-volume-status-should-show-bitrot-scrub-info.t index 89d2418e290..6101910666c 100644 --- a/tests/bugs/bitrot/1209752-volume-status-should-show-bitrot-scrub-info.t +++ b/tests/bugs/bitrot/1209752-volume-status-should-show-bitrot-scrub-info.t @@ -26,6 +26,9 @@ TEST $CLI_1 volume start $V0 ## Enable bitrot on volume $V0 TEST $CLI_1 volume bitrot $V0 enable +EXPECT_WITHIN $PROCESS_UP_TIMEOUT "2" get_bitd_count +EXPECT_WITHIN $PROCESS_UP_TIMEOUT "2" get_scrubd_count + ## From node 1 Gluster volume status command should show the status of bitrot ## daemon of all the nodes. there are 2 nodes in a cluster with having brick ## ${V0}1 and ${V0}2 . So there should be 2 bitrot daemon running. -- cgit