Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Running nosetests with multiprocessing tests on Windows leads to infinite explosion of processes #407
Create the following two files in a directory:
== run_nose.py =================
== test_me.py ==================
assert 1 < len(set(b)) <= 4
On Windows, if I go to the directory and type
...the tests run correctly. If I type
...it causes an exponential explosion of processes
(Note, be careful if you try it, in my case I need to have a command window open with "taskkill /F /IM python.exe" ready, otherwise the computer locks up fairly quickly.)
This does not seem to be entirely nose specific since "python setup.py test" seems to do the same thing in my project. But I'm wondering if you have any insight into what's going on here.
Python 2.7, Windows 7, nosetests-script.py version 1.0.0
See http://bugs.python.org/issue11240 for more information.
Google Code Info:
Sorry, forgot to mention: What seems to be happening in both cases ("nosetests" and "python setup.py test") based on the printed output is that each multiprocessing.Process that gets started executes the original command line ("nosetests" or "python setup.py test"), so each process starts running the test suite, causing an infinite fan-out.
Google Code Info:
We run the buildbot on both a Windows 7 64-bit environment and a Red Hat 5 64-bit environment both running Python 2.7.3. The Red Hat experiences no problems but the Windows 7 exhibits the same issue you have described. We have also tested with nose 1.1.2 and nose 1.3.0 and both exhibit this behavior.
The workaround will be ok for now as long as I can make it work with buildbot. Hopefully, this will get fixed soon.