From bae4981e85138e93663af9a5a35bb4be52bcfe27 Mon Sep 17 00:00:00 2001
From: Robert Kukura <kukura@noironetworks.com>
Date: Tue, 12 Sep 2017 18:19:37 -0400
Subject: [PATCH] Raise OS_TEST_TIMEOUT

Several apic_aim unit tests have been occasionally failing in the
gate, then passing when rechecked. This appears to be due to them
taking longer than 120 seconds to complete. We need to find out why
they take so long, and why the timing varies so much, but this should
help reduce the need to recheck in the mean time.

Change-Id: I6362d1cb6d7df87087282a6b78cabc741b31b9f1
---
 .testr.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.testr.conf b/.testr.conf
index 858fae61f..017887800 100644
--- a/.testr.conf
+++ b/.testr.conf
@@ -1,7 +1,7 @@
 [DEFAULT]
 test_command=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
              OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
-             OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-120} \
+             OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-180} \
              ${PYTHON:-python} -m subunit.run discover -t ./ ${OS_TEST_PATH:-./gbpservice} $LISTOPT $IDOPTION
 test_id_option=--load-list $IDFILE
 test_list_option=--list