This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients koobs, r.david.murray, skrah
Date 2015-06-23.10:53:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1435056818.24.0.848137866361.issue12210@psf.upfronthosting.co.za>
In-reply-to
Content
Those are in the second (or rather the first, in the file) group of tests, which have a timeout of 3 on python3.  The comment in the test case says that DNS lookup delays can cause timeouts.  Is there any chance that that machine sometimes has problems looking up 'localhost'?

There is no record in this issue of any change being applied to the tests, and I don't see any changes by Stefan in the file.

I suppose there's no real reason not to make all the timeouts 15 on both 2.7 and python3.  It is weird that those tests should take so long to run, but more likely to be an environment problem than a python code problem.  On the other hand, you might want to look in to why this is happening on FreeBSD, it might reveal something interesting.  

The problem with this theory, of course, is that we haven't apparently seen the timeouts on python3.  But I'm not sure what to look at to try to diagnose a difference...the smtplib code isn't that different between the two, so presumably if there is a real difference it is at the level of the socket code.  Since this is as far as we know only a test problem, we should probably just go ahead and increase the timeouts.
History
Date User Action Args
2015-06-23 10:53:38r.david.murraysetrecipients: + r.david.murray, skrah, koobs
2015-06-23 10:53:38r.david.murraysetmessageid: <1435056818.24.0.848137866361.issue12210@psf.upfronthosting.co.za>
2015-06-23 10:53:38r.david.murraylinkissue12210 messages
2015-06-23 10:53:38r.david.murraycreate