openstack
/
nova
Code Issues Proposed changes

Merge "Do not run tempest.scenario.test_network* tests in nova-next"

This commit is contained in:
Zuul 2019-03-09 14:18:16 +00:00 committed by Gerrit Code Review
parent 30550d3d94 f4387e4b66
commit 151deebde8
2 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.zuul.yaml
View File

@ -165,7 +165,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

7
playbooks/legacy/nova-next/run.yaml
View File

@ -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 {