Tox fails when run in local environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Erich Cordoba |
Bug Description
Brief Description
-----------------
Tox is no longer working in a local environment set up by following the instructions at https:/
This has been broken since the switch to opendev.
Severity
--------
Minor: This only affects designers in their development environment - tox runs properly from zuul.
Steps to Reproduce
------------------
Set up your local build environment and then attempt to run tox for a component. For example:
cd stx-nfv/nfv
tox
Expected Behavior
------------------
Tox should run the unit tests
Actual Behavior
----------------
Tox fails because the repo names have changed. The error will be something like this:
ERROR: could not install deps [./nfv-client, ./nfv-common, ./nfv-plugins, ./nfv-vim, ../../fault/fm-api, iso8601, keyring, kombu, kubernetes, passlib, pecan, pyparsing, PyYAML, sqlalchemy, stevedore, wsme, ./nfv-tests/
Reproducibility
---------------
Reproducible
System Configuration
-------
Development environment - does not affect the running system.
Branch/Pull Time/Commit
-------
Fails since the cutover to opendev on about April 20.
Last Pass
---------
Prior to the cutover to opendev.
Timestamp/Logs
--------------
See above
Test Activity
-------------
Developer unit testing
Changed in starlingx: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Erich Cordoba (ericho) |
The long-term fix for this is to remove the need to have hard-coded paths in places like tox.ini to find dependencies.
Until then, updating the manifest to use the new repo names is the quickest approach however that will require finding the remaining locations where those repo/directory names are hard-coded in the build system and other places.