[Python-Dev] test_multiprocessing: test_listener_client flakiness

Jean-Paul Calderone exarkun at divmod.com
Wed Jun 18 18:41:36 CEST 2008

On Wed, 18 Jun 2008 18:35:26 +0200, Amaury Forgeot d'Arc <amauryfa at gmail.com> wrote:
> [snip]
>I just found the cause of the problem ten minutes ago:
>It seems that when a socket listens on the address "" or
>"localhost", another process cannot connect to it using the machine's
>name (even from the same machine).

That's because when you try to connect to A:B you won't connect to a
server listening on X:B - somewhat by design.  Changing the test to
listen on A:B and X:B might fix it, but so would changing it to connect
to the same address it listens to.

>The best seems to listen with the empty address "".

This will cause it to listen on all available interfaces, including
public ones.  It's rather unlikely that someone from the internet
will connect to the port while the test suite is running and use it
to do terrible things to you, but it's not /impossible/.

I'd suggest changing the client to connect to "" or "localhost",


More information about the Python-Dev mailing list