tox doesn't support local testing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-midonet |
Fix Released
|
High
|
Boden R |
Bug Description
With the introduction tox sibilings with zuul v3 and removal of the install venv scripts, the local tox targets (pep8, py27, py3) don't properly setup the local env when running.
For example if you run "tox -py27" what gets installed is neutron 12.0.0 (as per requirements.txt), but what shoudl be installed is neutron/master.
To support proper testing envs locally (outside the zuul gate) a new target is needed that installs neutron from source.
For example we had to add a corresponding "-dev" tox target for each of these in vmware-nsx. EX: https:/
If tox doesn't support local testing its difficult to validate changes before submitting them, thus potentially wasting infra resources on simple issues that'd otherwise be caught in local testing.
Changed in networking-midonet: | |
importance: | Undecided → High |
milestone: | none → 7.0.0 |
status: | New → Confirmed |
Please see http:// lists.openstack .org/pipermail/ openstack- dev/2018- June/131801. html