[issue31596] expose pthread_getcpuclockid in time module

STINNER Victor added the comment: Thank you Benjamin, buildots are back to green :-) I prefer the new unit test which only tests pthread_getcpuclockid() clock and not make any assumption on the link between this clock and CLOCK_THREAD_CPUTIME_ID. --

[issue31596] expose pthread_getcpuclockid in time module

Benjamin Peterson added the comment: New changeset 86566702f311f8e90600e85350f6b6769a384ea5 by Benjamin Peterson in branch 'master': weaken pthread_getcpuclockid test (more bpo-31596) (#3904)

[issue31596] expose pthread_getcpuclockid in time module

Change by Benjamin Peterson : -- pull_requests: +3875 ___ Python tracker ___ ___

[issue31596] expose pthread_getcpuclockid in time module

pdox added the comment: This looks specific to FreeBSD and s390x. Those platforms might not provide the same cpu-time clock consistency guarantees as Linux+glibc+x86. Would it be ok to just disable the ordering check for those systems? --

[issue31596] expose pthread_getcpuclockid in time module

STINNER Victor added the comment: The test is too strict, it fails on many buildbots. Four examples: http://buildbot.python.org/all/builders/AMD64%20FreeBSD%2010.x%20Shared%203.x/builds/1008/steps/test/logs/stdio

[issue31596] expose pthread_getcpuclockid in time module

Benjamin Peterson added the comment: New changeset e14679c78464d1e0e16786c2a0e9bcebe49e842b by Benjamin Peterson (pdox) in branch 'master': closes bpo-31596: Add an interface for pthread_getcpuclockid(3) (#3756)

[issue31596] expose pthread_getcpuclockid in time module

New submission from pdox: time.clock_gettime() makes it possible to retrieve the thread-specific cpu-time clock for the current thread using time.CLOCK_THREAD_CPUTIME_ID. However, it is currently not possible in Python to retrieve the thread-specific clock for other threads. Exposing