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 kristjan.jonsson
Recipients jyasskin, kristjan.jonsson, pitrou
Date 2010-05-24.12:11:45
SpamBayes Score 0.04152647
Marked as misclassified No
Message-id <>
Well, I saw this occasionally on my dual core laptop when working on the RWLock.  A notify() before a target does a wait() is ineffective and it would wait indefinitely after the notify(5) call.  This isn't a "proper" fix (I had another, more complex, where we would keep a counter for the number of successful "waiters" and wait for that to reach the target value) but it is in the spirit of many of these tests, where we rely on _wait() to be sufficient to reach a certain state.
Date User Action Args
2010-05-24 12:11:47kristjan.jonssonsetrecipients: + kristjan.jonsson, pitrou, jyasskin
2010-05-24 12:11:47kristjan.jonssonsetmessageid: <>
2010-05-24 12:11:45kristjan.jonssonlinkissue8799 messages
2010-05-24 12:11:45kristjan.jonssoncreate