Yury Selivanov <yseliva...@gmail.com> added the comment:
Eric, it looks like your recent commit introduced a refleak. We need to fix it
before beta2.
~/d/p/cpython (master $) » ./python.exe -m test -R3:3 test_multiprocessing_fork
Run tests sequentially
0:00:00 load avg: 2.52 [1/1] test_multiprocessing_fork
beginning 6 repetitions
123456
......
test_multiprocessing_fork leaked [21, 2, 1] memory blocks, sum=24
test_multiprocessing_fork leaked [2, 0, 0] file descriptors, sum=2
test_multiprocessing_fork failed in 9 min 48 sec
1 test failed:
test_multiprocessing_fork
And just before it:
~/d/p/cpython ((bd093355…) $) » ./python.exe -m test -R3:3
test_multiprocessing_fork
Run tests sequentially
0:00:00 load avg: 3.70 [1/1] test_multiprocessing_fork
beginning 6 repetitions
123456
......
test_multiprocessing_fork passed in 9 min 12 sec
1 test OK.
Total duration: 9 min 12 sec
Tests result: SUCCESS
----------
priority: normal -> release blocker
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32604>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
