From aa09554f99e4c97846dd1d3fd47e980934cecc34 Mon Sep 17 00:00:00 2001 From: Sean Dague Date: Thu, 12 Nov 2015 16:38:52 -0500 Subject: [PATCH] always use constraints Running test jobs without constraints is mostly a recipe for tears, as it will allow for conflicting requirements which are no fun to debug. Remove any conditionality here. Change-Id: I51c916fa0a27b21b3342297f2a0e8563d1d5364c --- magnum/tests/contrib/post_test_hook.sh | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/magnum/tests/contrib/post_test_hook.sh b/magnum/tests/contrib/post_test_hook.sh index a84dff9c83..1b217e19d6 100755 --- a/magnum/tests/contrib/post_test_hook.sh +++ b/magnum/tests/contrib/post_test_hook.sh @@ -35,12 +35,7 @@ set -o xtrace echo_summary "magnum's post_test_hook.sh was called..." (set -o posix; set) -if [[ "$USE_CONSTRAINTS" == "True" ]]; then - constraints="-c $REQUIREMENTS_DIR/upper-constraints.txt" -else - constraints="" -fi -# XXX(lifeless) This should probably use setup_dev or some such. +constraints="-c $REQUIREMENTS_DIR/upper-constraints.txt" sudo pip install $constraints -U -r requirements.txt -r test-requirements.txt export MAGNUM_DIR="$BASE/new/magnum"