From 658b090e9b54580861f7355329b448a64c642b6e Mon Sep 17 00:00:00 2001
From: Atin Mukherjee <amukherj@redhat.com>
Date: Tue, 13 Jan 2015 11:52:13 +0530
Subject: tests: increase PROBE_TIMEOUT value to 60 secs

Its noticed that in a slower build system, nodes may take more than 20 secs to
finish the handshaking.
One of the recent regression failure
http://build.gluster.org/job/rackspace-regression-2GB-triggered/3635/consoleFull
is the proof for it.

Change-Id: Ibb69c51f31a697d5cb23bb688db80092c1de3047
BUG: 1163543
Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
Reviewed-on: http://review.gluster.org/9438
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Tested-by: Anand Nekkunti <anekkunt@redhat.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
---
 tests/include.rc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/include.rc b/tests/include.rc
index db79711d9e5..1e0e08cbb7c 100644
--- a/tests/include.rc
+++ b/tests/include.rc
@@ -54,7 +54,7 @@ DEBUG=${DEBUG:=0}             # turn on debugging?
 PROCESS_UP_TIMEOUT=20
 NFS_EXPORT_TIMEOUT=20
 CHILD_UP_TIMEOUT=20
-PROBE_TIMEOUT=20
+PROBE_TIMEOUT=60
 REBALANCE_TIMEOUT=360
 REOPEN_TIMEOUT=20
 HEAL_TIMEOUT=60
-- 
cgit