test-requirements are wrongly installed system-wide
Bug #1671144 reported by
Michal Ptacek
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Expired
|
Undecided
|
Unassigned |
Bug Description
test-requirements are installed system-wide
https:/
which is wrong as it might impact other system configuration
virtualenv concept was brought in
https:/
and most likely not covering test-requirements part properly
in our understanding there is gap in processing test-requirements where it's not configurable and always deployed system-wide
description: | updated |
Changed in devstack: | |
assignee: | nobody → Radek Zetik (radekx-zetik) |
Changed in devstack: | |
assignee: | Radek Zetik (radekx-zetik) → nobody |
status: | In Progress → New |
Changed in devstack: | |
assignee: | nobody → Radek Zetik (radekx-zetik) |
status: | New → In Progress |
To post a comment you must log in.
maybe a concert example of why this is bad is useful. /review. openstack. org/#/c/ 435575/ ts.txt file.
Michal works on the intel NFV CI and a recent change to nova
https:/
added a new requirement to the test-requiremen
following this change flake8-import-order is now installed systemwide.
as a result when we build ovs-dpdk from source in our thridparty ci
the automatic execution of pep8 testing as part of the ovs makefile
now fails due to the fact that openvswitch does not require strict ordering
of import for there python bindings.
as a result because the test-requirement are installed system wide instead of in virtual environments when they are run via tox the compilation of ovs was broken due to the introduction of a new test requrement to nova.
introducing a new devstack varible INSTALL_ TEST_REQS that wrapped /github. com/openstack- dev/devstack/ blob/6523d6e097 89076d0a430bf7b 608511fcb1c406a /inc/python# L336-L348
GLOBAL_
https:/
in an if would allow us to disable this behavior and also speed up our devstack deployment
as we do not run unit test in the thirdpart ci.
for the general devstack user it is also of benifit as you typically do not need the test-requirements for all project to be installed just the ones you contribute too and in this case
you will typically use tox to execute the test in a venv that will not use the system packages anyway.