From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 5/6] python3-more-itertools: upgrade 10.8.0 -> 11.1.0
Date: Wed, 07 Oct 2026 16:23:29 +0200 [thread overview]
Message-ID: <DLYOA1SGS44S.13W5W0AQMQTIH@bootlin.com> (raw)
In-Reply-To: <20261007055820.59633-5-jaipaul.cheernam@est.tech>
On Wed Oct 7, 2026 at 7:58 AM CEST, Jaipaul Cheernam wrote:
> changeLog: https://more-itertools.readthedocs.io/en/stable/versions.html#id1
>
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> ---
Hi Jaipaul,
It looks like ptests for python3-more-itertools are failing on riscv64
after this upgrade. It might be a timing issue, as usual.
{'python3-more-itertools': 'START: ptest-runner\n'
...
'tests/test_more.py:TestSynchronized.test_concurrent_calls\n'
'Timeout! System state:\n'
'Collected system state:\n'
Tried a few rebuilds, it did appear every times:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2563
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2564
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2565
Can you have a look at the issue? Maybe we need to relax the timings or
disable the test on riscv.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-10-07 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 5:58 [PATCH 1/6] cups: upgrade 2.4.19 -> 2.4.20 Jaipaul Cheernam
2026-10-07 5:58 ` [PATCH 2/6] harfbuzz: upgrade 14.5.1 -> 14.6.0 Jaipaul Cheernam
2026-10-07 5:58 ` [PATCH 3/6] rpm-sequoia-crypto-policy: upgrade to latest revision Jaipaul Cheernam
2026-10-07 5:58 ` [PATCH 4/6] python3-hypothesis: upgrade 6.168.3 -> 6.168.5 Jaipaul Cheernam
2026-10-07 5:58 ` [PATCH 5/6] python3-more-itertools: upgrade 10.8.0 -> 11.1.0 Jaipaul Cheernam
2026-10-07 14:23 ` Mathieu Dubois-Briand [this message]
2026-10-08 7:21 ` [OE-core] " Trevor Gamblin
2026-10-08 18:21 ` [PATCH v2] " Jaipaul Cheernam
2026-10-12 17:10 ` [OE-core] " Alexander Kanavin
2026-10-14 17:53 ` Jaipaul Cheernam
2026-10-07 5:58 ` [PATCH 6/6] python3-rpds-py: upgrade 2026.6.3 -> 2026.9.1 Jaipaul Cheernam
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=DLYOA1SGS44S.13W5W0AQMQTIH@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=jaipaul.cheernam@est.tech \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox