Georg Brandl added the comment:
2.5 years later I don't think it's much use keeping this open.
--
nosy: +georg.brandl
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6661
Sandro Tosi sandro.t...@gmail.com added the comment:
Hello,
what can we do with this issue? It doesn't seem it happened again after
Antoine's report (or at least no-one had followed it up) and it doesn't happen
nowdays (f.e. I exec'd test_multiprocessing in a loop for some time, and no
error
Stefan Krah stefan-use...@bytereef.org added the comment:
I've seen that one as well, but very rarely.
--
nosy: +skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6661
___
Sandro Tosi sandro.t...@gmail.com added the comment:
well, at least we have a confirmation it's still there :)
any idea how we can try to debug it?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6661
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
title: Transient test_multiprocessing failure - Transient test_multiprocessing
failure (test_active_children)
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6661
