[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-10-18 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: I'm going to close this as invalid: Python 3.3.2+ (3.3:247344a0d12e, Oct 18 2013, 13:14:59) [GCC 4.8.1] on linux Type help, copyright, credits or license for more information. from socket import * gethostbyname('in.val.id') Traceback (most recent call

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-10-18 Thread Barry A. Warsaw
Changes by Barry A. Warsaw ba...@python.org: -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17759 ___

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-08-25 Thread Ezio Melotti
Ezio Melotti added the comment: Apparently this has been fixed upstream in glibc: http://sourceware.org/bugzilla/show_bug.cgi?id=15339 There's also a related discussion at http://sourceware.org/bugzilla/show_bug.cgi?id=15726 Barry, can this be closed? -- nosy: +ezio.melotti type: -

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-08-25 Thread Antoine Pitrou
Antoine Pitrou added the comment: Works here on 13.04. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17759 ___ ___

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-08-25 Thread Yavor
Yavor added the comment: Within this note https://sourceware.org/glibc/wiki/NameResolver about getaddrinfo(): In case there was a *negative* answer it's unclear what should be returned. -- ___ Python tracker rep...@bugs.python.org

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-08-25 Thread Ezio Melotti
Ezio Melotti added the comment: FTR this got fixed (i.e. the timeout is ignored) in 3.3 (b17662fc41af) and default (6f8fef208958), but on 2.7. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17759

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-07-08 Thread Matthias Klose
Matthias Klose added the comment: ... that there is something abnormal with this Ubuntu release. no, it is not. This has nothing to do with Ubuntu, but is an upstream change introduced with glibc-2.17. So you will see it on every system which is based on the glibc version. see

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-07-07 Thread Yavor
Yavor added the comment: I have the same problem. Reproduced via custom app and what's failing is: getaddrinfo(some.invalid.address.here, NULL, hints, result); And it's failing quickly. But the returned error is system error 110 (Connection timed out). * A virtual machine inside same host -

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-07-07 Thread Yavor
Yavor added the comment: * Up-to-date Arch Linux: -2 - Name or service not known * Fedora Live CD: -2 - Name or service not known These are in general with more recent libraries/packages than Ubuntu 13.04. All evidences suggest that there is something abnormal with this Ubuntu release.

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-07-07 Thread Yavor
Yavor added the comment: Reported the issue to Ubuntu: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1198744 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17759 ___

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-04-16 Thread Barry A. Warsaw
New submission from Barry A. Warsaw: socket.gethostbyname('sadflkjsasf.i.nvali.d') gives a TimeoutError instead of an IOError on Ubuntu 13.04, causing the test to fail. % ./python -m unittest test.test_urllibnet .E../home/barry/projects/python/cpython/Lib/test/test_urllibnet.py:94:

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-04-16 Thread Matthias Klose
Matthias Klose added the comment: would be good to know if this is related to glibc-2.17, or not. There was a similiar issue ... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17759 ___

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-04-16 Thread R. David Murray
R. David Murray added the comment: I can't see how this could be classed as a bug in Python. An invalid domain should quickly return a DNS error on a correctly configured operating system, which is what the test is testing. If this report came from less well know names, I'd just close the

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-04-16 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Apr 16, 2013, at 03:26 PM, R. David Murray wrote: I can't see how this could be classed as a bug in Python. An invalid domain should quickly return a DNS error on a correctly configured operating system, which is what the test is testing. If this report

[issue17759] test_urllibnet.test_bad_address() fails on Ubuntu 13.04

2013-04-16 Thread R. David Murray
R. David Murray added the comment: OK, that makes sense. I leave it to you to close, I guess. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17759 ___