From eb354239a9f036a9e22e6f07daa03a7656948e4e Mon Sep 17 00:00:00 2001 From: Slawek Kaplonski Date: Tue, 14 Apr 2020 14:04:28 +0200 Subject: [PATCH] Set higher timeout for tests in scenario jobs It seems that in case of scenario tests which uses advanced image, when tests are run on slow node, it may happen that around 20 minutes test timeout will be not enough to perform all cleanup after test and it will fail due to that. So lets give more time for such tests to make sure all will be cleaned properly. Change-Id: Ic2177dc90a6fc8db4b50f05649ad794f6c3d5a23 Closes-Bug: #1872693 --- .zuul.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.zuul.yaml b/.zuul.yaml index 2e99198a..2a13d8c5 100644 --- a/.zuul.yaml +++ b/.zuul.yaml @@ -512,6 +512,10 @@ description: | Perform setup common to all tempest scenario test jobs. vars: + # NOTE(slaweq): in case of some tests, which requires advanced image, + # default test timeout set to 1200 seconds may be not enough if job is + # run on slow node + tempest_test_timeout: 2400 tempest_test_regex: ^neutron_tempest_plugin\.scenario devstack_localrc: PHYSICAL_NETWORK: default @@ -869,6 +873,10 @@ tempest_concurrency: 4 tox_envlist: all tempest_test_regex: ^neutron_tempest_plugin\.scenario + # NOTE(slaweq): in case of some tests, which requires advanced image, + # default test timeout set to 1200 seconds may be not enough if job is + # run on slow node + tempest_test_timeout: 2400 network_api_extensions_common: *api_extensions_master network_api_extensions_dvr: - dvr