Charles-François Natali added the comment: > Some ftplib tests sometimes time out. Seem they seem to try to connect to > "localhost" (rather than "127.0.0.1"), I was wondering if this could be a DNS > issue and if we should resolve "localhost" in advance like Charles-François > did for some other tests (or simply hardcode "127.0.0.1", actually).
If it only happens on Windows >= 7 buildbots, then it's likely a consequence of this: http://serverfault.com/questions/4689/windows-7-localhost-name-resolution-is-handled-within-dns-itself-why Apparently, since Windows 7, "localhost" doesn't appear in the hosts file anymore: so, depending on your DNS resolver settings, this could perfectly explain such timeouts (assuming it's not a firewall issue). Hard-cording 127.0.0.1 for this test should be OK, because the server setup explicitly binds an AF_INET socket. We'll probably have to check the rest of the test suite for similar issues. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18792> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
