You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently zope-testrunner -jN runs the first test layer serially, and only then starts forking N subprocesses for parallel execution. People have been creating workarounds for this by adding an empty test layer named something like .!no tests here! to get the 1st serial layer out of the way ASAP, so the rest of the tests can run in parallel.
Suggestion: if the test runner sees -j on the command line, let it create an empty test layer automatically and insert it in front of all other layers. (Maybe make it conditional on there being at least two other layers, maybe don't bother -- who would use -j when there's only one test layer?)
The text was updated successfully, but these errors were encountered:
BTW fixing this will make the regression test for #6 invalid. The test should probably be rewritten to avoid -j and instead explicitly define a test layer that does os.chdir() and raises NotImplementedError from layer teardown.
agroszer
added a commit
to agroszer/zope.testrunner
that referenced
this issue
May 19, 2015
Currently zope-testrunner -jN runs the first test layer serially, and only then starts forking N subprocesses for parallel execution. People have been creating workarounds for this by adding an empty test layer named something like
.!no tests here!
to get the 1st serial layer out of the way ASAP, so the rest of the tests can run in parallel.The change in 4.4.5 (run the unit test layer first, https://bugs.launchpad.net/zope.testrunner/+bug/497871) broke this hack.
Suggestion: if the test runner sees -j on the command line, let it create an empty test layer automatically and insert it in front of all other layers. (Maybe make it conditional on there being at least two other layers, maybe don't bother -- who would use -j when there's only one test layer?)
The text was updated successfully, but these errors were encountered: