openstack/neutron-tempest-plugin
Code Issues Proposed changes

Set higher timeout for tests in scenario jobs

Browse Source 
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
This commit is contained in:
Slawek Kaplonski 2020-04-14 14:04:28 +02:00
parent 22d7cc950b
commit eb354239a9
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
.zuul.yaml
View File

@ -512,6 +512,10 @@
description: | description: |
Perform setup common to all tempest scenario test jobs. Perform setup common to all tempest scenario test jobs.
vars: 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 tempest_test_regex: ^neutron_tempest_plugin\.scenario
devstack_localrc: devstack_localrc:
PHYSICAL_NETWORK: default PHYSICAL_NETWORK: default
@ -869,6 +873,10 @@
tempest_concurrency: 4 tempest_concurrency: 4
tox_envlist: all tox_envlist: all
tempest_test_regex: ^neutron_tempest_plugin\.scenario 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_common: *api_extensions_master
network_api_extensions_dvr: network_api_extensions_dvr:
- dvr - dvr