You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2018-07-06.15:45:51.082>created_at=<Date2018-07-05.16:33:47.826>labels= ['3.8', '3.7', 'library']
title='multiprocessing should use time.monotonic() for timeout'updated_at=<Date2018-07-06.15:45:51.081>user='https://github.com/vstinner'
In different functions, the multiprocessing module uses the system clock: time.time(). The system clock can be updated manually by the system administrator or automatically by NTP (for example).
Attached PR modifies multiprocessing to use time.monotonic() instead to not be affected by system clock changes.
time.monotonic() is always available since Python 3.5. See also the PEP-418.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: