On Wed, 11 Aug 2021 at 18:14, Mike Crowe <[email protected]> wrote: > I agree regarding the lack of explanation. However, even if the problem is > real (which it looks like it is based on > https://bugs.python.org/issue41710) > then it wouldn't be expected to cause test failures unless the system clock > was being warped at inconvenient times during the tests. >
So can we just patch python to use the right glibc function with the right clock type, and send the patch upstream then? Much better than the workaround that was merged. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#154726): https://lists.openembedded.org/g/openembedded-core/message/154726 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]] -=-=-=-=-=-=-=-=-=-=-=-
