Browse code
rebuild the tempest tox env during install
When redoing a stack.sh over and over again, tempest venv can get out
of sync and cause issues until deleted. We should rebuild that tempest
venv on every stack.
Change-Id: I2f66bb1a7ccf9f89e11db1326d8553589e52fbf2
Sean Dague authored on 2017/03/22 00:15:05Showing 1 changed files
| ... | ... |
@@ -618,7 +618,7 @@ function install_tempest {
|
| 618 | 618 |
git_clone $TEMPEST_REPO $TEMPEST_DIR $TEMPEST_BRANCH |
| 619 | 619 |
pip_install tox |
| 620 | 620 |
pushd $TEMPEST_DIR |
| 621 |
- tox --notest -efull |
|
| 621 |
+ tox -r --notest -efull |
|
| 622 | 622 |
# NOTE(mtreinish) Respect constraints in the tempest full venv, things that |
| 623 | 623 |
# are using a tox job other than full will not be respecting constraints but |
| 624 | 624 |
# running pip install -U on tempest requirements |