Do not run tempest.scenario.test_network* tests in nova-next
The test_network* scenario tests in tempest take a really long time. For example, the tempest.scenario.test_network_v6.TestGettingAddress tests in one job (that timed out) took ~35 minutes. We already run test network scenario tests in the tempest-slow job so let's just let that job handle these and exclude them from nova-next. Change-Id: I9c7fc0f0b0937f04c5b3ab9c5e8fff21c4232b86
This commit is contained in:
parent
dfaa513fe1
commit
f4387e4b66
|
@ -164,7 +164,7 @@
|
|||
TLS console proxy code in the libvirt driver.
|
||||
Starting in Stein, the job was changed to run with python 3 and enabled
|
||||
volume multi-attach testing.
|
||||
Runs all tempest compute API and scenario tests concurrently.
|
||||
Runs all tempest compute API and most scenario tests concurrently.
|
||||
run: playbooks/legacy/nova-next/run.yaml
|
||||
post-run: playbooks/legacy/nova-next/post.yaml
|
||||
|
||||
|
|
|
@ -60,9 +60,12 @@
|
|||
export PYTHONUNBUFFERED=true
|
||||
# Yes we want to run Tempest.
|
||||
export DEVSTACK_GATE_TEMPEST=1
|
||||
# Run all compute API tests and all scenario tests at the default
|
||||
# Run all compute API tests and most scenario tests at the default
|
||||
# concurrency (nproc/2 which is normally 4 in the gate).
|
||||
export DEVSTACK_GATE_TEMPEST_REGEX="^tempest\.((scenario)|(api\.compute))"
|
||||
# The tempest.scenario.test_network* tests are skipped because they
|
||||
# (1) take a long time and (2) are already covered in the
|
||||
# tempest-slow* job.
|
||||
export DEVSTACK_GATE_TEMPEST_REGEX="^tempest\.((scenario(?!\.test_network))|(api\.compute))"
|
||||
# The post_test_hook runs some post-test CLIs for things that
|
||||
# Tempest does not test, like archiving deleted records.
|
||||
function post_test_hook {
|
||||
|
|
Loading…
Reference in New Issue