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 eacb, r.david.murray
Date 2015-06-08.01:55:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433728531.19.0.00756695746813.issue24397@psf.upfronthosting.co.za>
In-reply-to
Content
The comments in the test indicate that this possibility was considered and dealt with.  So that indicates it is a test bug in this particular test (test_close_when_done, for other readers), not in the fixture.  It looks like the race condition still exists, the window is just reduced.  Can you see any reason the assert shouldn't be moved to before the s.start_reserved_event.set()?  (Since I missed the clearing of the buffer, I'm not confident in my reading of the test intent :)
History
Date User Action Args
2015-06-08 01:55:31r.david.murraysetrecipients: + r.david.murray, eacb
2015-06-08 01:55:31r.david.murraysetmessageid: <1433728531.19.0.00756695746813.issue24397@psf.upfronthosting.co.za>
2015-06-08 01:55:31r.david.murraylinkissue24397 messages
2015-06-08 01:55:30r.david.murraycreate