tox doesn't support local testing

Bug #1778271 reported by Boden R
6
This bug affects 1 person
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://github.com/openstack/vmware-nsx/blob/master/tox.ini#L83

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.

Revision history for this message
Boden R (boden) wrote :
Changed in networking-midonet:
importance: Undecided → High
milestone: none → 7.0.0
status: New → Confirmed
Revision history for this message
Boden R (boden) wrote :

I submitted [1] which should address this for master branch (only).

[1] https://review.openstack.org/#/c/578212/

Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :
Changed in networking-midonet:
assignee: nobody → Boden R (boden)
status: Confirmed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on networking-midonet (master)

Change abandoned by boden (<email address hidden>) on branch: master
Review: https://review.openstack.org/578212
Reason: superceeded https://review.openstack.org/#/c/604211/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.