Message196167
| Author |
ezio.melotti |
| Recipients |
Stan.Seibert, asksol, brandon-rhodes, catalin.iacob, christian.heimes, dholth, ezio.melotti, gregory.p.smith, jnoller, mrmekon, ned.deily, neologix, numbernine, pitrou, python-dev, rcoyner, sbt, vsekhar |
| Date |
2013年08月25日.21:54:42 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1377467682.99.0.0293140168972.issue8713@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年08月25日 21:54:43 | ezio.melotti | set | recipients:
+ ezio.melotti, gregory.p.smith, pitrou, christian.heimes, ned.deily, jnoller, rcoyner, asksol, dholth, brandon-rhodes, neologix, catalin.iacob, python-dev, sbt, numbernine, vsekhar, mrmekon, Stan.Seibert |
| 2013年08月25日 21:54:42 | ezio.melotti | set | messageid: <1377467682.99.0.0293140168972.issue8713@psf.upfronthosting.co.za> |
| 2013年08月25日 21:54:42 | ezio.melotti | link | issue8713 messages |
| 2013年08月25日 21:54:42 | ezio.melotti | create |
|