Order of Tests in tox.ini Causes Failure
Bug #1415446 reported by
Terry Howe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Python Jenkins |
Fix Released
|
Undecided
|
Unassigned | ||
python-neutronclient |
Fix Released
|
Undecided
|
Terry Howe |
Bug Description
Order of tests in tox.ini causes a failure because of an incompatibility in the test repository. If py27 or py26 tests are run before py33 or py34, the py3 tests fail.
Changed in python-neutronclient: | |
assignee: | nobody → Terry Howe (thowe-g) |
status: | New → In Progress |
Changed in python-neutronclient: | |
milestone: | none → 2.3.11 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/143657 /git.openstack. org/cgit/ openstack/ python- neutronclient/ commit/ ?id=6f7cd146726 391c5fe37d2e64e a57469319f455a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 6f7cd146726391c 5fe37d2e64ea574 69319f455a
Author: Terry Howe <email address hidden>
Date: Tue Dec 23 05:09:42 2014 -0700
Reverse order of tests to avoid incompatibility
If py26 tests are run first, there is a incompatibility in the
.testrepository that breaks several tests. To get around this, you
need to run the py33 tests first. This change was made over in the
cliff project.
Before:
...
py26: commands succeeded
py27: commands succeeded
ERROR: py33: commands failed
ERROR: py34: commands failed
ERROR: pypy: commands failed
pep8: commands succeeded
After:
...
py33: commands succeeded
py34: commands succeeded
py26: commands succeeded
py27: commands succeeded
pypy: commands succeeded
pep8: commands succeeded
Closes-Bug: 1415446
Change-Id: Ia0b44cc4a05dd1 c668204d8d4dce5 381d35373fe