From 7cd32c18a11d0dfeb70c276b0185e21d06a71fa5 Mon Sep 17 00:00:00 2001 From: Pranith Kumar K Date: Mon, 19 May 2014 13:29:06 +0530 Subject: tests: Use uniform timeouts Change-Id: I479ab941b3b2da3b16f624400fbd300f08326268 BUG: 1092850 Signed-off-by: Pranith Kumar K Reviewed-on: http://review.gluster.org/7799 Tested-by: Gluster Build System Reviewed-by: Anand Avati --- tests/bugs/bug-765473.t | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'tests/bugs/bug-765473.t') diff --git a/tests/bugs/bug-765473.t b/tests/bugs/bug-765473.t index 5fc0ec9d77e..d9af751f472 100755 --- a/tests/bugs/bug-765473.t +++ b/tests/bugs/bug-765473.t @@ -11,7 +11,7 @@ function clients_connected() volname=$1 gluster volume status $volname clients | grep -i 'Clients connected' | sed -e 's/[^0-9]*\(.*\)/\1/g' } - + ## Start and create a volume TEST glusterd; TEST pidof glusterd; @@ -27,7 +27,7 @@ TEST $CLI volume stop $V0 # write some content which will result in marking fd bad fd_write $fd "more content" TEST $CLI volume start $V0 -EXPECT_WITHIN 30 2 clients_connected $V0 +EXPECT_WITHIN $PROCESS_UP_TIMEOUT 2 clients_connected $V0 TEST ! fd_write $fd "still more content" cleanup -- cgit