[issue3419] multiprocessing module is racy

[Mark Dickinson]

Mark Dickinson <dickinsm at gmail.com> added the comment:

> Are you looking at the conn refused or the incref error?

The connection refused error.

The attached patch fixes the problem, for me.  On my machine, the 
connection refused error code was 61 rather than 10061.  With this patch, 
I'm no longer seeing any hangs in test_multiprocessing.py (at least, not in 
the last 500 runs :-)).  (Though I am still seeing the incref error 
occasionally.)

If anyone's prepared to answer a stupid question:  I'm curious why failed 
socket connections occur at all.  Is connecting to a socket generally 
considered an unreliable operation, or is there some aspect of the 
multiprocessing module that makes it potentially unreliable?

----------
keywords: +patch
Added file: http://bugs.python.org/file11038/mp_nohang.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3419>
_______________________________________