8d5fbf9388
Make sure to test that log messages are being emitted and captured correctly across a larger number of tests to catch issues in tests incorrectly polluting the setup of the logging capturing across other test cases exposed by a recent patch. Where tests are executed in separate threads it is possible for a mistake in one thread, thrashing the logging capture to go unnoticed unless other tests being executed in the same thread are checking for correct log output. This can result in random failures as the test execution order is dependent on PYTHONHASHSEED. This change ensures that most tests being executed perform a positive assertion for content to appear in the logged output, at one of the standard log levels (as opposed to the custom one) to ensure that logging is being captured correctly by the test framework. Change-Id: I903478d6f3cb3f25dd7e2410c78155eca6a7d780 Related-Patch: https://review.openstack.org/387426 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| drop.py | ||
| help.py | ||
| import.py | ||
| supersede.py | ||