From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <Pascal.Weisser.ext@karlstorz.com>,
<openembedded-core@lists.openembedded.org>
Cc: "Weisser, Pascal" <pascal.weisser.ext@karlstorz.com>
Subject: Re: [OE-core] [PATCH 0/3] Resolve YOCTO #14520 and YOCTO #15525.
Date: Wed, 19 Mar 2025 10:33:12 +0100 [thread overview]
Message-ID: <D8K50W97LGL8.1WRT66MJ5ZYV1@bootlin.com> (raw)
In-Reply-To: <20250318104853.1442703-1-pascal.weisser.ext@karlstorz.com>
On Tue Mar 18, 2025 at 11:48 AM CET, Pascal.ext via lists.openembedded.org Weisser wrote:
> This patch series resolves the issues YOCTO #14520 and YOCTO #15525.
>
> Weisser, Pascal (3):
> Revert "qemuboot: Trigger write_qemuboot_conf task on changes of
> kernel image realpath"
> qemuboot: Trigger do_write_qemuboot_conf task on bundled initramfs
> changes
> qemuboot: Provide default value for INITRAMFS_LINK_NAME
>
> meta/classes-recipe/qemuboot.bbclass | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Hi Pascal,
Thanks for your patch.
I believe this is creating circular dependencies in some cases: we got a
few errors on the autobuilder:
ERROR:
Dependency loop #1 found:
Task /srv/pokybuild/yocto-worker/genericarm64-alt/build/meta/recipes-core/images/core-image-initramfs-boot.bb:do_image_complete (dependent Tasks ['qemu-system-native_9.2.0.bb:do_populate_sysroot', 'core-image-initramfs-boot.bb:do_image', 'core-image-initramfs-boot.bb:do_image_cpio', 'core-image-initramfs-boot.bb:do_write_qemuboot_conf', 'qemu-helper-native_1.0.bb:do_addto_recipe_sysroot'])
Task /srv/pokybuild/yocto-worker/genericarm64-alt/build/meta/recipes-kernel/linux/linux-yocto_6.12.bb:do_bundle_initramfs (dependent Tasks ['core-image-initramfs-boot.bb:do_image_complete', 'linux-yocto_6.12.bb:do_install'])
Task /srv/pokybuild/yocto-worker/genericarm64-alt/build/meta/recipes-kernel/linux/linux-yocto_6.12.bb:do_deploy (dependent Tasks ['depmodwrapper-cross_1.0.bb:do_populate_sysroot', 'linux-yocto_6.12.bb:do_populate_sysroot', 'linux-yocto_6.12.bb:do_packagedata', 'pigz_2.8.bb:do_populate_sysroot', 'linux-yocto_6.12.bb:do_bundle_initramfs'])
Task /srv/pokybuild/yocto-worker/genericarm64-alt/build/meta/recipes-core/images/core-image-initramfs-boot.bb:do_write_qemuboot_conf (dependent Tasks ['linux-yocto_6.12.bb:do_deploy', 'core-image-initramfs-boot.bb:do_rootfs'])
https://autobuilder.yoctoproject.org/valkyrie/#/builders/22/builds/1218
https://autobuilder.yoctoproject.org/valkyrie/#/builders/60/builds/1215
Can you have a look at these failures please?
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-03-19 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:48 [PATCH 0/3] Resolve YOCTO #14520 and YOCTO #15525 Weisser, Pascal
2025-03-18 10:48 ` [PATCH 1/3] Revert "qemuboot: Trigger write_qemuboot_conf task on changes of kernel image realpath" Weisser, Pascal
2025-03-18 10:48 ` [PATCH 2/3] qemuboot: Trigger do_write_qemuboot_conf task on bundled initramfs changes Weisser, Pascal
2025-03-18 10:48 ` [PATCH 3/3] qemuboot: Provide default value for INITRAMFS_LINK_NAME Weisser, Pascal
2025-03-19 9:33 ` Mathieu Dubois-Briand [this message]
2025-03-28 9:21 ` [PATCH 0/3] Resolve YOCTO #14520 and YOCTO #15525 Weisser, Pascal.ext
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=D8K50W97LGL8.1WRT66MJ5ZYV1@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=Pascal.Weisser.ext@karlstorz.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 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.