Set python hash seed to 0 in tox.ini

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
This commit is contained in:
Jeremy Stanley 2014-09-22 23:14:50 +00:00
parent 92e21e47ef
commit 44e144b15f

View File

@ -7,10 +7,13 @@ skipsdist = True
sitepackages = True
usedevelop = True
install_command = pip install -U {opts} {packages}
# Note the hash seed is set to 0 until gce-api can be tested with a
# random hash seed successfully.
setenv = VIRTUAL_ENV={envdir}
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_ALL=C
PYTHONHASHSEED=0
deps = -r{toxinidir}/requirements.txt
-r{toxinidir}/test-requirements.txt
commands =
@ -27,13 +30,11 @@ commands =
flake8 {posargs}
[testenv:pylint]
setenv = VIRTUAL_ENV={envdir}
commands = bash tools/lintstack.sh
[testenv:cover]
# Also do not run test_coverage_ext tests while gathering coverage as those
# tests conflict with coverage.
setenv = VIRTUAL_ENV={envdir}
commands =
python tools/patch_tox_venv.py
python setup.py testr --coverage \