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 ned.deily
Recipients dfarrell07, ned.deily, python-dev, r.david.murray
Date 2014-03-27.09:13:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
After pushing the changes for Issue20939, many of the buildbots started experiencing the test_fileno failure using  The interesting thing is that not all of them do, including my primary development system (OS X 10.9) which is why I didn't see a problem during the initial testing.  On another dev system (Debian Linux on a VM), the test fails intermittently. So, yes, something funky *is* going on.  One obvious difference is that the read from returns 44000+ byes while returns only 162 bytes.  There could be a race condition with the TCP connection close.  I've temporarily changed the test to use pending resolution. Thanks for the report and investigation, Daniel.
Date User Action Args
2014-03-27 09:13:32ned.deilysetrecipients: + ned.deily, r.david.murray, python-dev, dfarrell07
2014-03-27 09:13:32ned.deilysetmessageid: <>
2014-03-27 09:13:32ned.deilylinkissue21069 messages
2014-03-27 09:13:31ned.deilycreate