Ezio Melotti added the comment: The new tests produce a few warnings: $ ./python -m test -uall test_multiprocessing_spawn [1/1] test_multiprocessing_spawn Using start method 'spawn' Warning -- threading._dangling was modified by test_multiprocessing_spawn Warning -- multiprocessing.process._dangling was modified by test_multiprocessing_spawn
$ ./python -m test -uall -v -j2 test_multiprocessing_fork OK (skipped=4) Warning -- threading._dangling was modified by test_multiprocessing_fork Warning -- multiprocessing.process._dangling was modified by test_multiprocessing_fork 1 test altered the execution environment: test_multiprocessing_fork I've seen test_multiprocessing_forkserver giving warnings too, while running the whole test suite, but can't reproduce them while running it alone. The warnings seems quite similar though, so a single fix might resolve the problem with all the tests. The "Using start method '...'" should also be displayed only when the tests are run in verbose mode. ---------- nosy: +ezio.melotti _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8713> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com