From 83408e8ba04e61849a182f2003d5360bc155a224 Mon Sep 17 00:00:00 2001 From: kshithijiyer Date: Mon, 24 Feb 2020 12:05:18 +0530 Subject: [Testfix] Fix timeout issue in test_heal_full_node_reboot Problem: The current timeout for reboot given in test_heal_full_node_reboot is about 350 seconds which works with most hardware configurations. However when reboot is done on slower systems which take time to come up this logic fails due to which this testcase and the preceding testcases fail. Solution: Change the timeout for reboot from 350 to 700, this wouldn't affect the testcase's perfromance in good hardware configurations as the timeout is for the max value and if the node is up before the testcase it'll exit anyways. Change-Id: I60d05236e8b08ba7d0fec29657a93f2ae53404d4 Signed-off-by: kshithijiyer --- .../disperse/test_ec_verify_datacorruption_during_full_heal.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests') diff --git a/tests/functional/disperse/test_ec_verify_datacorruption_during_full_heal.py b/tests/functional/disperse/test_ec_verify_datacorruption_during_full_heal.py index 6d91ee0c6..f9b480e41 100644 --- a/tests/functional/disperse/test_ec_verify_datacorruption_during_full_heal.py +++ b/tests/functional/disperse/test_ec_verify_datacorruption_during_full_heal.py @@ -195,7 +195,7 @@ class TestHealFullNodeReboot(GlusterBaseClass): # Check if nodes are online counter = 0 - timeout = 350 + timeout = 700 _rc = False while counter < timeout: ret, reboot_results = are_nodes_online(nodes_to_reboot) -- cgit