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 Sebastian.Noack, asvetlov, christian.heimes, jyasskin, kristjan.jonsson, mklauber, neologix, pitrou, sbt
Date 2012-10-05.09:51:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349430703.03.0.621193317288.issue8800@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks Richard.
I wonder if the issues with the multiprocessing tests can be fixed by making use of Barriers?

One of the reasons I introduced Barriers into the lib originally was my alarm at seeing the various springklings of different _wait() calls in the unittests, particularly in the threading module (there are Condition variable tests there still that have race conditions, that are cunnrently hidden by liberal use of _wait())

Then I started to wonder if it were appropriate to use a Barrier in the Condition variable tests, particularly given that the former is implemented by way of the latter :)
History
Date User Action Args
2012-10-05 09:51:43kristjan.jonssonsetrecipients: + kristjan.jonsson, pitrou, christian.heimes, jyasskin, asvetlov, neologix, sbt, mklauber, Sebastian.Noack
2012-10-05 09:51:43kristjan.jonssonsetmessageid: <1349430703.03.0.621193317288.issue8800@psf.upfronthosting.co.za>
2012-10-05 09:51:42kristjan.jonssonlinkissue8800 messages
2012-10-05 09:51:41kristjan.jonssoncreate