Changes by R. David Murray rdmur...@bitdance.com:
--
keywords: +buildbot
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6748
___
___
Antoine Pitrou pit...@free.fr added the comment:
Please note that the Windows buildbot shows another error:
==
ERROR: test_debuglevel (test.test_telnetlib.OptionTests)
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
priority: - normal
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6748
___
Antoine Pitrou pit...@free.fr added the comment:
This failure actually still happens quite regularly (on the buildbots
and also on my Mandriva system).
Judging from a quick Google search, errno 104 (ECONNRESET) should be
treated as a case of EOF (it means the TCP connection was reset using
RST
Derk Drukker derk.druk...@gmail.com added the comment:
This patch fixes the issue.
--
keywords: +patch
nosy: +drukker
Added file: http://bugs.python.org/file15242/issue6748.patch
___
Python tracker rep...@bugs.python.org
Eric Smith e...@trueblade.com added the comment:
I still get 'Connection reset by peer' on OS/X 10.5.8 with this patch
(http://bugs.python.org/file15242/issue6748.patch).
--
nosy: +eric.smith
___
Python tracker rep...@bugs.python.org
Jack Diederich jackd...@gmail.com added the comment:
Antoine Pitrou: Besides, the test flow in test_telnetlib really is a
mess (setUp and tearDown getting called multiple times, for example),
could you clean it up?
Yes, I'm working on refactoring the test server and separating out
testing that
Derk Drukker derk.druk...@gmail.com added the comment:
The change in the patch worked for me on py3k on Ubuntu 9.10. It makes
sense, though, that it could still fail: conn can get closed too soon.
--
___
Python tracker rep...@bugs.python.org
