All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <Qi.Chen@windriver.com>, <openembedded-core@lists.openembedded.org>
Cc: <alex.kanavin@gmail.com>, <randy.macleod@windriver.com>
Subject: Re: [OE-core][PATCH V5 1/7] recipeutils: add optional stable_upgrade parameter to get_recipe_upgrade_status
Date: Thu, 14 May 2026 12:38:33 +0200	[thread overview]
Message-ID: <DIIC2A22J8TH.2IC6O1ZQ1MODS@bootlin.com> (raw)
In-Reply-To: <20260513052334.2271800-1-Qi.Chen@windriver.com>

On Wed May 13, 2026 at 7:23 AM CEST, Chen Qi via lists.openembedded.org wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> We want the ability to do stable version upgrades for recipes.
> To this end, add an optional stable_upgrade parameter to the
> get_recipe_upgrade_status function, which defaults to False and
> when enabled will try to get the latest stable version of the recipe.
>
> The UPSTREAM_STABLE_RELEASE_REGEX is respected. If a recipe sets
> it, it will be used as the filter_regex. If it's not set explicitly,
> it means that there's no stable updates or the recipe hasn't been
> checked yet.
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---

Hi Chen,

Thanks for the new version.

We got several selftest fails on the autobuilder:

2026-05-13 20:05:23,677 - oe-selftest - INFO - overlayfs.OverlayFSTests.test_mount_unit_not_set (subunit.RemotedTestCase)
2026-05-13 20:05:23,678 - oe-selftest - INFO -  ... FAIL
...
ERROR: /srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-37462/meta-selftest/recipes-test/overlayfs-user/overlayfs-user.bb: A recipe uses overlayfs class but there is no OVERLAYFS_MOUNT_POINT set in your MACHINE configuration
ERROR: Parsing halted due to errors, see error messages above
...
2026-05-13 20:11:59,345 - oe-selftest - INFO - overlayfs.OverlayFSTests.test_wrong_mount_unit_set (subunit.RemotedTestCase)
2026-05-13 20:11:59,345 - oe-selftest - INFO -  ... FAIL
...
2026-05-13 20:22:13,763 - oe-selftest - INFO - recipetool.RecipetoolAppendTests.test_recipetool_appendfile_add_bindir (subunit.RemotedTestCase)
2026-05-13 20:22:13,764 - oe-selftest - INFO -  ... FAIL
...
2026-05-13 20:23:11,171 - oe-selftest - INFO - recipetool.RecipetoolAppendTests.test_recipetool_appendfile_add_machine (subunit.RemotedTestCase)
2026-05-13 20:23:11,172 - oe-selftest - INFO -  ... FAIL
...
2026-05-13 20:24:48,333 - oe-selftest - INFO - recipetool.RecipetoolAppendTests.test_recipetool_appendfile_basic (subunit.RemotedTestCase)
2026-05-13 20:24:48,334 - oe-selftest - INFO -  ... FAIL
...

https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3951
https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/3850
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3718

Can you have a look at this issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2026-05-14 10:38 UTC|newest]

Thread overview: 16+ 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 [this message]
2026-05-15  9:06   ` Chen, Qi
2026-05-15 10:22     ` Alexander Kanavin
2026-05-15 11:00     ` Mathieu Dubois-Briand

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=DIIC2A22J8TH.2IC6O1ZQ1MODS@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=Qi.Chen@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.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.