[issue12539] multiprocessing.Event.wait(n) doesn't time out properly

Charles-François Natali added the comment: >> Are you using a 2.6.38 kernel? > Yes Alright, closing as invalid then. -- resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue12539] multiprocessing.Event.wait(n) doesn't time out properly

mokrates added the comment: > Are you using a 2.6.38 kernel? Yes > There was a regression in early 2.6.38 kernels that caused FUTEX_WAIT > with a timeout to never return after a suspend-resume, see: > https://lkml.org/lkml/2011/4/13/23 Ah, thank you, that explains why gajim has problems too..

[issue12539] multiprocessing.Event.wait(n) doesn't time out properly

Charles-François Natali added the comment: Are you using a 2.6.38 kernel? There was a regression in early 2.6.38 kernels that caused FUTEX_WAIT with a timeout to never return after a suspend-resume, see: https://lkml.org/lkml/2011/4/13/23 It's been fixed by this commit: http://git.kernel.org/?

[issue12539] multiprocessing.Event.wait(n) doesn't time out properly

New submission from mokrates : Following is my problem: I have two processes, connected via multiprocessing.Event The one waits for the other with .wait(300). After 300 seconds it should look if there's work, even if it has not been awoken by the other process. So. This runs on my Laptop, and wh