From e60649e08ce6b1b01d1480bc06433007c9c320ee Mon Sep 17 00:00:00 2001 From: ShunliZhou Date: Thu, 1 Jun 2017 10:20:05 +0800 Subject: [PATCH] Change the tempest test interval to 2s. Always seen tempest test fail with api timeout error. Refer to http://logs.openstack.org/42/469342/2/check/ gate-zun-devstack-dsvm-docker-sql/02b4650/ logs/apache/zun_api.txt.gz#_2017-05-31_08_29_52_459 But run the tempest in local devstack, the logs show there are lots of rabbitmq messages and seems the rabbitmq cannot handle so much message. Checked the code there are lots of check status called in tempest test. So this patch propose to change the check status interval to 2s to reduce the numbers of messages to avoid rabbitmq message stuck. Change-Id: Ibb41ae552bcce0f685834e13a6c3a5836f657cab --- zun/tests/tempest/utils.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zun/tests/tempest/utils.py b/zun/tests/tempest/utils.py index c61b92e1f..dd6498901 100644 --- a/zun/tests/tempest/utils.py +++ b/zun/tests/tempest/utils.py @@ -13,7 +13,7 @@ import time -def wait_for_condition(condition, interval=1, timeout=60): +def wait_for_condition(condition, interval=2, timeout=60): start_time = time.time() end_time = time.time() + timeout while time.time() < end_time: