homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pablogsal
Recipients ido k, pablogsal, vstinner
Date 2019年01月16日.22:15:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1547676933.73.0.413545194298.issue35747@roundup.psfhosted.org>
In-reply-to
Content
I think this is becase at the end, the threading code calls
sem_timedwait(thelock, &ts) where &ts is the timespect structure. The manpage of sem_timedwait says:
...
The timeout shall expire when the absolute time specified by abs_timeout passes, as measured by the clock on which timeouts are based (that is, when the value of that clock equals or exceeds abs_timeout), or if the absolute time specified by abs_timeout has already been passed at the time of the call.
If the Timers option is supported, the timeout shall be based on the CLOCK_REALTIME clock. If the Timers option is not supported, the timeout shall be based on the system clock as returned by the time() function. The resolution of the timeout shall be the resolution of the clock on which it is based. The timespec data type is defined as a structure in the <time.h> header.
So I assume this is using the system clock, so is affected by the date.
History
Date User Action Args
2019年01月16日 22:15:35pablogsalsetrecipients: + pablogsal, vstinner, ido k
2019年01月16日 22:15:33pablogsalsetmessageid: <1547676933.73.0.413545194298.issue35747@roundup.psfhosted.org>
2019年01月16日 22:15:33pablogsallinkissue35747 messages
2019年01月16日 22:15:33pablogsalcreate

AltStyle によって変換されたページ (->オリジナル) /