goodbye and good riddance, run_tests.sh
Bug #1172012 reported by
Aaron Rosen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Low
|
Unassigned |
Bug Description
Quantum has been using tox for more than 6 months now, and it's about time to remove run_tests.sh, which apparently does not even work anymore.
This bug description has been updated to reflect consensus from the community.
Changed in quantum: | |
status: | New → Confirmed |
Changed in neutron: | |
assignee: | Salvatore Orlando (salvatore-orlando) → nobody |
To post a comment you must log in.
This is likely the result of having switched to testr but run_test.sh not having been updated. Note that the way the gate runs it is 'tox -e pep8', and this still works. Invoking flake8 directly also works, and will pick up the configuration from tox.ini
There was a session at the summit questioning whether run_tests.sh should persist given that tox can do the same thing and maintaining parity isn't free. Another concern was that run_tests.sh hides the underlying command being executed from developers, and it might be preferable to require people to invoke a given command directly so that they can have the opportunity to discover more advanced features (e.g. testr --failing).
So, should this bug be fixed, or might it be preferable to seek consensus on removal of run_tests.sh instead?