Many tests fail when run with random hash seed value
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Undecided
|
Marian Horban |
Bug Description
When runing the test suite with a random hash seed, eg
PYTHONHASHSEED=666 ./run_tests.sh
many tests will fail as iterators over hash keys/values change their ordering. For example there are many failures in libvirt like
=======
FAIL: nova.tests.
-------
Traceback (most recent call last):
_StringException: Empty attachments:
stderr
stdout
pythonlogging:'': {{{
INFO [nova.network.
WARNING [nova.virt.
INFO [nova.network.
WARNING [nova.virt.
}}}
Traceback (most recent call last):
File "/home/
expect_
File "/home/
(check(tree), expected_result, i))
File "/home/
self.
File "/home/
raise mismatch_error
MismatchError: '8388608' != '2097152': 8388608 != 2097152 failed common check 1
As well as failures across many other tests suites.
This bug is to track resolution of all problems in Nova seen when setting PYTHONHASHSEED to a non-zero value.
tags: | added: network |
Changed in nova: | |
assignee: | Christopher Yeoh (cyeoh-0) → nobody |
Changed in nova: | |
assignee: | nobody → Christopher Yeoh (cyeoh-0) |
NB a workaround was applied in this review to force the hash seed to 0 for tox, until the proper fixes are done. https:/ /review. openstack. org/#/c/ 109700/