use master upper-constraints when building tempest venv

The local requirements repo can be checked out to a stable branch,
in which case, the requirements might conflict with tempest's master
requirements.

Master branch's upper-constraints should be used when building tempest's
venv.

Closes-Bug: #1706009

Change-Id: Ifd64638cae2886671421149dbbff3a57f9c64257
(cherry picked from commit 34c1679f2e)
This commit is contained in:
Claudiu Belu 2017-06-12 09:32:21 -07:00 committed by Ghanshyam Mann
parent 19337acada
commit 56f5a5d6d9
1 changed files with 4 additions and 1 deletions

View File

@ -542,7 +542,10 @@ function configure_tempest {
if [[ "$OFFLINE" != "True" ]]; then
tox -revenv-tempest --notest
fi
tox -evenv-tempest -- pip install -c $REQUIREMENTS_DIR/upper-constraints.txt -r requirements.txt
# The requirements might be on a different branch, while tempest needs master requirements.
git -C $REQUIREMENTS_DIR show master:upper-constraints.txt > u-c-m.txt
tox -evenv-tempest -- pip install -c u-c-m.txt -r requirements.txt
# Auth:
iniset $TEMPEST_CONFIG auth tempest_roles "Member"