Browse code

Stop installing test-requirements with projects

This is a test of installing openstack and then seeing if it works.
OpenStack components do not need test-requirements to operate,
that's why they are test-requirements.

Additionally, as we look forward to depsolver pip, this is going
to screw us because we don't apply constraints to linters, which
are expressed in - you guessed it, test-requirements.

Change-Id: I8f24b839bf42e2fb9803dc7df3a30ae20cf264eb

Monty Taylor authored on 2020/03/28 01:22:39
Showing 1 changed files
... ...
@@ -179,13 +179,6 @@ function pip_install {
179 179
 
180 180
     $xtrace
181 181
 
182
-    # Also install test requirements
183
-    local install_test_reqs=""
184
-    local test_req="${package_dir}/test-requirements.txt"
185
-    if [[ -e "$test_req" ]]; then
186
-        install_test_reqs="-r $test_req"
187
-    fi
188
-
189 182
     # adding SETUPTOOLS_SYS_PATH_TECHNIQUE is a workaround to keep
190 183
     # the same behaviour of setuptools before version 25.0.0.
191 184
     # related issue: https://github.com/pypa/pip/issues/3874
... ...
@@ -195,7 +188,7 @@ function pip_install {
195 195
         no_proxy="${no_proxy:-}" \
196 196
         PIP_FIND_LINKS=$PIP_FIND_LINKS \
197 197
         SETUPTOOLS_SYS_PATH_TECHNIQUE=rewrite \
198
-        $cmd_pip $upgrade $install_test_reqs \
198
+        $cmd_pip $upgrade \
199 199
         $@
200 200
     result=$?
201 201