[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Floris Bruynooghe added the comment: Oops, I've kicked the bruynooghe-solaris-csw buildslave and it should now be building again. A bit disappointed that buildbot/twisted doesn't reconnect automatically though. -- ___ Python tracker

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

R. David Murray added the comment: buildbot does normally reconnect automatically, so something must be wrong somewhere if it didn't. I do seem to remember a bug that caused the slave to occasionally get confused about its current status in certain unusual circumstances...perhaps that bug

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Mark Lawrence added the comment: I'm guessing that this would have been resolved some time ago, am I correct? -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

STINNER Victor added the comment: I'm guessing that this would have been resolved some time ago, am I correct? You should not guess but check last builds of SPARC Solaris 10 OpenCSW 3.x to see if the issue stil occurs.

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Mark Lawrence added the comment: By following the link I finally get to see No current builds. Pending Build Requests: (Apr 30 15:07:05, waiting 1445 hrs, 32 mins, 26 secs). Is there any way that I can tell from the display whether or not the failures are related to this issue? --

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

koobs added the comment: Incase it helps at all, I'm seeing the test failure preparing for adding python33 to the FreeBSD ports tree. On FreeBSD 9.0-RELEASE-p3 (amd64), with /etc/hosts configured as follows: ::1 localhost.domain localhost 127.0.0.1

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Floris Bruynooghe added the comment: I have no issue with changing the buildhost's zone configuration if that's the right thing to do. Just one more option. Is widening the expected errno in the test a valid thing to do? -- ___ Python tracker

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Antoine Pitrou added the comment: I wonder how other systems respond to [...] if all interfaces except for lo are down On Mageia Linux 1: socket.getaddrinfo('localhost', 80, 0, socket.SOCK_STREAM, 0, socket.AI_ADDRCONFIG) Traceback (most recent call last): File stdin, line 1, in module

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Martin v. Löwis added the comment: Antoine: thanks for the report. I fear that this rules out using AI_ADDRCONFIG: IETF has managed to break it. This is really silly. So I'm tempted to close this as won't fix. Comments? Build slaves would be required that a regular lookup of localhost matches

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

New submission from Floris Bruynooghe: The SPARC Solaris 10 OpenCSW 3.x builder fails with == FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

R. David Murray added the comment: But if getaddrinfo returns an IPv6 address, shouldn't a localhost connection on that address work? It seems to me that a localhost connection failing when an IPv6 localhost address is returned is an OS configuration bug. -- nosy: +r.david.murray

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Floris Bruynooghe added the comment: It was my understanding that this is what the AI_ADDRCONFIG flag is for, if you don't use it you have no such guarantee. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15617

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

R. David Murray added the comment: That sounds reasonable. However, on my box that has an IPv6 address configured on lo, I get the same result with or without that flag: loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Floris Bruynooghe added the comment: I think this is influenced by what you have in /etc/hosts. On my laptop I also have IPv6 loopback as well as an IPv6 link-local on eth0. But I have both 127.0.0.1 and ::1 in /etc/hosts as locahost. With that configuration I get the same getaddrinfo results

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15617 ___ ___ Python-bugs-list

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Martin v. Löwis added the comment: I was about to say that I agree that AI_ADDRCONFIG should be used in create_connection. However, RFC 3493 deviates from RFC 2553 by stating If the AI_ADDRCONFIG flag is specified, IPv4 addresses shall be returned only if an IPv4 address is configured on

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

R. David Murray added the comment: Hmm. I wonder what is different on my (linux) box. I have ::1 in /etc/hosts for localhost. Regardless, it certainly wouldn't hurt to add the flag to the test. -- ___ Python tracker rep...@bugs.python.org

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

Martin v. Löwis added the comment: David: I get the same on Linux as you, however, in the standard Debian installation, ::1 is *not* an address for localhost, only for ip6-localhost and ip6-loopback. Likewise, on Redhat, it seems that only localhost6 gives you ::1. What Linux distribution are

[issue15617] FAIL: test_create_connection (test.test_socket.NetworkConnectionNoServer)

R. David Murray added the comment: I see our previous messages crossed, I'm glad you investigated this more throughly than I did, since clearly just adding the flag could break things. I'm using gentoo linux (gentoo stable on that particular machine). I don't guarantee my /etc/hosts file is