According to Openstack summit session [1] stestr is
maintained project to which all Openstack projects
should migrate.
Let's switch it then.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: If3383707c9baf69e03bcccc50970da748a834141
Adopt the timeout override fixture from nova.
Borrowed from I591f3c270804dfb01eab7c8c5d43b87a7abcdeda
Co-Authored-By: Sean Dague <sean@dague.net>
Closes-Bug: #1626277
Change-Id: I0b40ce97ba42d55f048e9728d9f032ada5c85100
Revert the change I4c88f1891f53c6559bca71bf657aa30df2101280.
The testtools bug was fixed, the "| cat" workaround is no more
needed.
Fix for subunit (for testtools), workaround the eventlet bug:
https://github.com/testing-cabal/subunit/pull/14
Fix of the root cause in eventlet:
https://github.com/eventlet/eventlet/issues/248
The bug was limited to Python 3 and related to non-blocking stdout.
See also the similar change for oslo.messaging:
I207b7a7e82cbd7e5848231115b3577be7b600638.
Change-Id: Iad759af7fbd8a404b7ac361763b27214f3a49ac3
Related-Bug: 1492505
This change is in support of adding a new jenkins job dedicated
to functional testing. Functional tests will no longer be
run as part of the unit tests.
Change-Id: Ia99940f7e5a2165720ae2a74aadf62ff17ad3d75
Interacting with a long-running asynchronous process requires the
use of non-blocking io. This change adds a helper class that can
launch a long-running process and read stdout and stderr in a
non-blocking fashion via eventlet.
This functionality is intended to support monitoring ovsdb via
a long-running and root-privileged invocation of ovsdb-client.
The complexity of the system interaction in this patch suggested
the addition of a functional test that validated actual behaviour.
The test was added under the neutron/tests/functional path which
is now included in the testr search path.
Partial-Bug: #1177973
Change-Id: I9969e556acecf7a9e77d873371cc2ec2647be011
Viewing log output while tests are still running can be useful for
debugging, but log output was previously always captured. This
change ensures that log capture is off by default, but can still
be enabled by setting OS_LOG_CAPTURE=1 in the shell environment.
testr invocation is unchanged and will continue to capture logs by
default.
Change-Id: I9d0fb648541280cacfebb47f67f608378ae66ef3
This change renames everything to Neutron while providing backwards
compatible adjustments for Grizzly configuration files.
implements blueprint: remove-use-of-quantum
Change-Id: Ie7d07ba7c89857e13d4ddc8f0e9b68de020a3d19
* The old behavior required setting environment variables to
disable capture of stdout and stderr to allow debugging via pdb.
The new behavior requires enabling capture of stdout/stderr
instead. This is already the case in nova.
* testr behavior is unmodified.
* Tip 'o the hat to Robert Collins (lifeless)
Change-Id: Ica021eeab07d5a540ce42436c9cc8000c3fd239a
This doesn't really do much other that add the needed bits to the repo to
start hacking on testr support in small chunks.
Change-Id: I34fc57fdc7c9ebda8ffa2357a2ef962c7ab41bfa
Slawek Kaplonski