[issue7547] test_timeout should skip, not fail, when the remote host is not available
Antoine Pitrou
report at bugs.python.org
Sat Dec 19 17:45:04 CET 2009
New submission from Antoine Pitrou <pitrou at free.fr>:
test_timeout uses www.python.org as a Guinea pig for its socket tests.
Unfortunately sometimes www.python.org is down, which gives the
following kind of failures (seen on a buildbot recently):
test test_timeout failed -- Traceback (most recent call last):
File "C:\buildslave\3.x.moore-windows\build\lib\test\test_timeout.py",
line 133, in testRecvTimeout
self.sock.connect(self.addr_remote)
socket.error: [Errno 10060] A connection attempt failed because the
connected party did not properly respond after a period of time, or
established connection failed because connected host has failed to respond
test_timeout should catch the error and simply skip the test with an
appropriate message.
There's a similar problem with test_smtpnet which uses gmail as its
remote SMTP-SSL provider.
----------
components: Tests
messages: 96615
nosy: pitrou
priority: normal
severity: normal
stage: needs patch
status: open
title: test_timeout should skip, not fail, when the remote host is not available
type: behavior
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue7547>
_______________________________________
More information about the Python-bugs-list
mailing list