Message 139135 - Python tracker

➜

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	vstinner
Recipients	neologix, vstinner
Date	2011-06-26.00:42:55
SpamBayes Score	0.0006795462
Marked as misclassified	No
Message-id	<1309048975.99.0.281047921612.issue12413@psf.upfronthosting.co.za>
In-reply-to

Content
> since all the processes receive the signal at the same time, > their outputs will be interleaved (we could maybe add a random > sleep before dumping the traceback?) And we have the pid list of the children, we can use an arbitrary sleep (e.g. 1 second) before sending a signal to the next pid. Anyway, a sleep is the most reliable synchronization code after a crash/timeout.

> since all the processes receive the signal at the same time,
> their outputs will be interleaved (we could maybe add a random
> sleep before dumping the traceback?)

And we have the pid list of the children, we can use an arbitrary sleep (e.g. 1 second) before sending a signal to the next pid. Anyway, a sleep is the most reliable synchronization code after a crash/timeout.

History
Date	User	Action	Args
2011-06-26 00:43:09	vstinner	unlink	issue12413 messages
2011-06-26 00:42:56	vstinner	set	recipients: + vstinner, neologix
2011-06-26 00:42:55	vstinner	set	messageid: <1309048975.99.0.281047921612.issue12413@psf.upfronthosting.co.za>
2011-06-26 00:42:55	vstinner	link	issue12413 messages
2011-06-26 00:42:55	vstinner	create