From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Chen, Qi" <Qi.Chen@windriver.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "alex.kanavin@gmail.com" <alex.kanavin@gmail.com>,
"MacLeod, Randy" <Randy.MacLeod@windriver.com>
Subject: Re: [OE-core][PATCH V5 1/7] recipeutils: add optional stable_upgrade parameter to get_recipe_upgrade_status
Date: Fri, 15 May 2026 13:00:43 +0200 [thread overview]
Message-ID: <DIJ75SUU12NB.1RALWVIO1OS58@bootlin.com> (raw)
In-Reply-To: <CO6PR11MB5602B1780BBA2AD5C925D884ED042@CO6PR11MB5602.namprd11.prod.outlook.com>
On Fri May 15, 2026 at 11:06 AM CEST, Qi Chen wrote:
> Hi Mathieu,
>
> I can't reproduce this issue.
Hi Chen,
Yes, I confirm I have the same issue on my side: I can't reproduce the
failures locally.
Yet I confirm the issue is linked with this series: dropping the patches
solves the issue, and I have similar issues with the v4. It's not clear
why in only happens on the autobuilder.
If you have ideas you want to test on the autobuilder to debug it, I can
easily schedule some builds. Aside of that, I fear I have no better
solution right now, I'm sorry.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-05-15 11:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 5:23 [OE-core][PATCH V5 1/7] recipeutils: add optional stable_upgrade parameter to get_recipe_upgrade_status Qi.Chen
2026-05-13 5:23 ` [OE-core][PATCH V5 2/7] upstream-stable-release-point.bbclass: add bbclass for stable point upgrade Qi.Chen
2026-05-13 5:23 ` [OE-core][PATCH V5 3/7] vte: inherit upstream-stable-release-point Qi.Chen
2026-05-13 5:23 ` [OE-core][PATCH V5 4/7] systemd: " Qi.Chen
2026-05-13 5:23 ` [OE-core][PATCH V5 5/7] kmod: " Qi.Chen
2026-05-13 5:23 ` [OE-core][PATCH V5 6/7] util-linux: " Qi.Chen
2026-05-13 5:23 ` [OE-core][PATCH V5 7/7] openssh: set UPSTREAM_STABLE_RELEASE_REGEX Qi.Chen
2026-05-13 9:35 ` [OE-core][PATCH V5 1/7] recipeutils: add optional stable_upgrade parameter to get_recipe_upgrade_status Alexander Kanavin
2026-05-13 9:44 ` Daniel Turull
2026-05-13 9:51 ` Alexander Kanavin
2026-05-14 4:27 ` Chen, Qi
2026-05-14 4:16 ` Chen, Qi
2026-05-14 10:38 ` Mathieu Dubois-Briand
2026-05-15 9:06 ` Chen, Qi
2026-05-15 10:22 ` Alexander Kanavin
2026-05-18 2:37 ` ChenQi
2026-05-18 4:09 ` Alexander Kanavin
2026-05-18 5:55 ` ChenQi
2026-05-15 11:00 ` Mathieu Dubois-Briand [this message]
2026-05-18 3:07 ` ChenQi
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=DIJ75SUU12NB.1RALWVIO1OS58@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=Qi.Chen@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=alex.kanavin@gmail.com \
--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