openstack
/
blazar
Code Issues Proposed changes

Set Tempest concurrency to one 

We are going to add API tests using Gabbi to the blazar-tempest-plugin.
But if the Gabbi tests are executed by different workers, their order
gets violated.

This patch changes Tempest concurrency to 1 to ensure the Gabbi tests
are executed in the order specified in the YAML file. This can increase
test execution time, but it should be negligible.

Change-Id: Id4dc3cc8640e8f902f96130a85e50008b5e8b96d
This commit is contained in:
Tetsuro Nakamura 2018-07-11 19:14:04 +09:00 committed by Hiroaki Kobayashi
parent 84785b7dde
commit 4253cb0fd2
2 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
playbooks/legacy/blazar-devstack-dsvm-py35/run.yaml
View File

@ -57,6 +57,7 @@
export PROJECTS="openstack/python-blazarclient $PROJECTS"
export PROJECTS="openstack/blazar-tempest-plugin $PROJECTS"
export DEVSTACK_GATE_TEMPEST_REGEX="blazar_tempest_plugin"
export TEMPEST_CONCURRENCY=1
cp devstack-gate/devstack-vm-gate-wrap.sh ./safe-devstack-vm-gate-wrap.sh
./safe-devstack-vm-gate-wrap.sh
executable: /bin/bash

1
playbooks/legacy/blazar-devstack-dsvm/run.yaml
View File

@ -49,6 +49,7 @@
export PROJECTS="openstack/python-blazarclient $PROJECTS"
export PROJECTS="openstack/blazar-tempest-plugin $PROJECTS"
export DEVSTACK_GATE_TEMPEST_REGEX="blazar_tempest_plugin"
export TEMPEST_CONCURRENCY=1
cp devstack-gate/devstack-vm-gate-wrap.sh ./safe-devstack-vm-gate-wrap.sh
./safe-devstack-vm-gate-wrap.sh
executable: /bin/bash