From: "Mike Crowe" <yocto@mac.mcrowe.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Ross Burton <ross@burtonini.com>,
"Zhang, Qiang" <qiang.zhang@windriver.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] python3: use monotonic clock for condvar if possible
Date: Wed, 11 Aug 2021 17:57:02 +0100 [thread overview]
Message-ID: <20210811165702.GA14091@mcrowe.com> (raw)
In-Reply-To: <CANNYZj-am4poZ6hahsUw5R3He8hny5EP7CLXRQSLXRP2TCVR-w@mail.gmail.com>
On Wednesday 11 August 2021 at 18:32:31 +0200, Alexander Kanavin wrote:
> On Wed, 11 Aug 2021 at 18:14, Mike Crowe <mac@mcrowe.com> 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.
In theory, yes. I've no idea how hard that is though. It probably requires
adding build-time detection of whether the new functions are available to
avoid breaking other/older target operating systems.
Mike.
prev parent reply other threads:[~2021-08-11 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 5:11 [OE-core] [PATCH] python3: use monotonic clock for condvar if possible Zhang, Qiang
2021-08-09 15:45 ` Steve Sakoman
2021-08-09 17:53 ` Ross Burton
2021-08-11 11:36 ` Alexander Kanavin
2021-08-11 16:14 ` Mike Crowe
2021-08-11 16:32 ` Alexander Kanavin
2021-08-11 16:57 ` Mike Crowe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210811165702.GA14091@mcrowe.com \
--to=yocto@mac.mcrowe.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=qiang.zhang@windriver.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross@burtonini.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.