To be co-installable with other OpenStack projects and have consistent
testing it's a good idea (tm) to use constraints when creating tox
environments.
Change-Id: I753eba5de69388d98b616eef7d12054539b279f8
Remove the last remaining references to Oslo incubator in the project
as this is no longer used, and no longer supported.
Adjust tox configuration to no longer require tools scripts to define
Oslo incubator venv.
Change-Id: I8d012a8e784386892a28ab476d2e87afdd2657fd
Once we add debug testenv, we can use "tox debug -- --debug"
to debug test cases when tox is running.
Change-Id: I6f56257e4bbe3f9e303c014f169f016c5668269e
Python 3.3 support would be dropped by
Infra team from mitaka,CI would no longer be testing it,
so projects should drop it also.
Change-Id: I7d3e377b4ce05caf2606d493ddd18b9bff3add4d
To solve the problem of "db type could
not be determined" on py34 we have to run first the py34 env to, then, run
py27. This patch puts py34 first on the tox.ini list of envs to avoid this
problem to happen.
Change-Id: Ide061d82c130231e653c91e6a9c8db8b43225535
Closes-bug: #1489059
Tox egenconfig fails because its using ec2api instead
of gceapi. also the readme was named as ec2api which
is fixed in this patch.
Change-Id: I1a7b4462f53339077e13385e84e043b096cbc2ed
New tox (>=1.7.0) sets a random python hash seed by default. This is
generally good for testing because it will help keep projects working
regardless of the hash seed, but nova unittests don't currently pass
with a random hash seed so set it to the python default seed.
This change will allow us to use new tox again and remove the
restriction on tox<=1.6.1 to run unittests.
Redundant setenvs for specific test envs are removed to prevent them
from overriding the PYTHONHASHSEED value.
Note this change will need to be backported to the stable branches to
keep unittests there working with new tox as well.
Change-Id: Ib1dc229c0a678dd5324712baa25404aff08f9581
Co-Authored-By: Clark Boylan <clark.boylan@gmail.com>
Related-Bug: #1348818
Tony Breeds