[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

Change by STINNER Victor : -- resolution: fixed -> duplicate superseder: -> NewGIL should use CLOCK_MONOTONIC if possible. ___ Python tracker ___ _

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

STINNER Victor added the comment: See bpo-41710 "Timeout is affected by jumps in system time". -- ___ Python tracker ___ ___ Python

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

STINNER Victor added the comment: INADA-san fixed bpo-12822 with: New changeset 001fee14e0f2ba5f41fb733adc69d5965925a094 by Inada Naoki in branch 'master': bpo-12822: use monotonic clock for condvar if possible (GH-11723) https://github.com/python/cpython/commit/001fee14e0f2ba5f41fb733adc69d5

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

Change by INADA Naoki : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.8 -Python 3.5 ___ Python tracker ___ ___

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

Pablo Galindo Salgado added the comment: > One workaround is to use Python to use the mutex+cond implementation of > pthread locks, since this one is already able to use CLOCK_MONOTONIC: Does this have any drawbacks? -- ___ Python tracker

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

Pablo Galindo Salgado added the comment: > One workaround is to use Python to use the mutex+cond implementation of > pthread locks, since this one is already able to use CLOCK_MONOTONIC: That this have any drawbacks? -- nosy: +pablogsal ___ Python

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

Change by Andrey Ovchinnikov : -- nosy: +anikey ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

STINNER Victor added the comment: See also bpo-12822: "NewGIL should use CLOCK_MONOTONIC if possible". -- ___ Python tracker ___ __

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

STINNER Victor added the comment: > Is there any progress on the issue? Should someone take over? It's a limitation of the libc, not directly of Python. The problem is that the sem_timedwait() function of the glibc doesn't allow to specify which clock is used: https://sourceware.org/bugzilla

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

STINNER Victor added the comment: I closed bpo-35747 "Python threading event wait influenced by date change" as a duplicate of the issue. -- ___ Python tracker ___ __

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

STINNER Victor added the comment: I marked bpo-31267 "threading.Timer object is affected by changes to system time: Python locks should use a monotonic clock if available" as a duplicate of this issue. -- ___ Python tracker

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

Change by Erik Bray : -- pull_requests: +4856 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

Charalampos Stratakis added the comment: Hello, Is there any progress on the issue? Should someone take over? -- nosy: +cstratak ___ Python tracker ___ _

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

STINNER Victor added the comment: Oh, I missed the issue #12822 which looks to fix similar bugs. -- ___ Python tracker ___ ___ Python-

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

Changes by STINNER Victor : -- nosy: +neologix ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

STINNER Victor added the comment: cond_timedwait_monotonic.patch: Work-in-progress patch. It doesn't change configure.ac yet to check if pthread_condattr_setclock() is supported (with CLOCK_MONOTONIC). -- keywords: +patch Added file: http://bugs.python.org/file38069/cond_timedwait_mono

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

STINNER Victor added the comment: > Python/condvar.h and Python/thread_pthread.h should use the monotonic clock > CLOCK_MONOTONIC Oh, I forgot that Python/thread_pthread.h only uses pthread_cond_timedwait() if semaphores are emulated with mutexes+conditional variables. On most platforms, PyTh

[issue23428] Use the monotonic clock for thread conditions on POSIX platforms

New submission from STINNER Victor: Python 3.5 now requires a monotonic clock to start and has the C function _PyTime_monotonic(). Python/condvar.h and Python/thread_pthread.h should use the monotonic clock CLOCK_MONOTONIC, not the system clock CLOCK_REALTIME. See the PEP 418 for the rational