Message320967
Hum. Sadly my commit 23401fb960bb94e6ea62d2999527968d53d3fc65 is not enough, the test still fails randomly:
pydev@stormageddon ~/cpython $ ./python -m test test_multiprocessing_forkserver -m test_imap_unordered -R 3:3 -F
Run tests sequentially
0:00:00 load avg: 5.79 [ 1] test_multiprocessing_forkserver
beginning 6 repetitions
123456
......
0:00:28 load avg: 6.98 [ 2] test_multiprocessing_forkserver
beginning 6 repetitions
123456
......
0:00:59 load avg: 7.69 [ 3] test_multiprocessing_forkserver -- test_multiprocessing_forkserver passed in 30 sec 717 ms
beginning 6 repetitions
123456
......
0:01:28 load avg: 8.63 [ 4] test_multiprocessing_forkserver
beginning 6 repetitions
123456
......
test_multiprocessing_forkserver leaked [2, 1, 1] memory blocks, sum=4
test_multiprocessing_forkserver failed
== Tests result: FAILURE ==
3 tests OK.
1 test failed:
test_multiprocessing_forkserver
Total duration: 1 min 55 sec
Tests result: FAILURE
The test failed when the system load was high (8.63).
I hope that in pratice, my change will be enough to get less random failures. The "Re-run in verbose mode" on the "idle" buildbot should make the bug disappear. |
|
Date |
User |
Action |
Args |
2018-07-03 11:40:06 | vstinner | set | recipients:
+ vstinner |
2018-07-03 11:40:06 | vstinner | set | messageid: <1530618006.91.0.56676864532.issue33984@psf.upfronthosting.co.za> |
2018-07-03 11:40:06 | vstinner | link | issue33984 messages |
2018-07-03 11:40:06 | vstinner | create | |
|