diff options
| author | Brian Rosmaita <rosmaita.fossdev@gmail.com> | 2021-07-29 17:44:23 -0400 |
|---|---|---|
| committer | Brian Rosmaita <rosmaita.fossdev@gmail.com> | 2021-07-29 22:04:01 -0400 |
| commit | d04ded6a6ff4cc9ba8377a1b025493e939047b2c (patch) | |
| tree | 3e612c8abcae85304a1bd88de01472b3b088ff43 | |
| parent | e03111dea33d671661d01eadbb068d6ee6987cec (diff) | |
| download | python-cinderclient-d04ded6a6ff4cc9ba8377a1b025493e939047b2c.tar.gz | |
Unset tempest.lib timeout in functional tests
The test_cli.CinderBackupTests.test_backup_create_and_delete test
is hitting timeout errors in the python-cinderclient-functional-py36
zuul job. This is happening because it's inheriting the
OS_TEST_TIMEOUT value of 60 from the base testenv, and that value is
being used by the tempest.lib class we inherit from as a timeout for
each test. This is a problem for test_backup_create_and_delete
because it creates a volume, waits for available, creates a backup,
waits for available, deletes the volume, waits for deletion, deletes
the backup, waits for deletion.
Our functional tests have their own timeout handling, so turn off
the tempest.lib timeout and use ours. An alternative to turning it
off is to set it at a value that respects our timeout for our longest
test, which would be:
- time-to-available: 120 sec (x2)
- time-to-deleted: 60 sec (x2)
that is, 360 sec.
Change-Id: I33399b4c094af2cc059da6e332f4c0a91e6ab57e
| -rw-r--r-- | tox.ini | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -84,6 +84,11 @@ setenv = OS_VOLUME_API_VERSION = 3 # must define this here so it can be inherited by the -py3* environments OS_CINDERCLIENT_EXEC_DIR = {envdir}/bin + # Our functional tests contain their own timeout handling, so + # turn off the timeout handling provided by the + # tempest.lib.base.BaseTestCase that our ClientTestBase class + # inherits from. + OS_TEST_TIMEOUT=0 # The OS_CACERT environment variable should be passed to the test # environments to specify a CA bundle file to use in verifying a |