[New-bugs-announce] [issue31991] Race condition in wait with timeout for multiprocessing.Event

Thomas Moreau report at bugs.python.org
Thu Nov 9 08:48:13 EST 2017


New submission from Thomas Moreau <thomas.moreau.2010 at gmail.com>:

If the methods `set` and `clear` of `multiprocessing.Event` are called one after another, while a `multiprocessing.Process` calls `wait`, the  `Event` does not match the documented behavior (https://docs.python.org/3.7/library/threading.html#threading.Event.wait) and the call to wait can return `False` even though the call to wait did not timeout (This happens both with `timeout=30` or `timeout=None`).

Attached is a script reproducing this issue.
The documentation should either be changed or the behavior should be updated.

----------
components: Library (Lib)
files: concurrent_event.py
messages: 305960
nosy: tomMoral
priority: normal
severity: normal
status: open
title: Race condition in wait with timeout for multiprocessing.Event
type: behavior
versions: Python 3.6
Added file: https://bugs.python.org/file47256/concurrent_event.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31991>
_______________________________________


More information about the New-bugs-announce mailing list