I too do not think this is sufficiently explained. All of python ptests pass, so there needs to be a demonstrator of incorrect behavior, or let's just revert it.
Alex On Mon, 9 Aug 2021 at 19:53, Ross Burton <[email protected]> wrote: > On Tue, 3 Aug 2021 at 05:41, Zhang, Qiang <[email protected]> > wrote: > > The timeout for threading.Lock, threading.Condition, etc, is not using > > a monotonic clock, it is affected if the system time (realtime clock) > > is set. > > > > This patch will make condvar use monotonic clock. > > Refence: https://bugs.python.org/issue41710 > > That doesn't quite make sense to me. > > As referenced in that bug report, > > https://github.com/python/cpython/commit/001fee14e0f2ba5f41fb733adc69d5965925a094 > uses monotonic clocks by default. That was in 3.8.0 onwards. > > So, why is this change to pretend that the semaphore is broken needed? > > Ross > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#154718): https://lists.openembedded.org/g/openembedded-core/message/154718 Mute This Topic: https://lists.openembedded.org/mt/84632397/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
