From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 3/3] oeqa selftest uboot.py: add qemu KVM test case
Date: Tue, 27 May 2025 12:55:15 +0300 [thread overview]
Message-ID: <aDWMA7d77g-JX4p4@nuoska> (raw)
In-Reply-To: <DA6UBTHJ83S9.34WKJTD4HEHZK@bootlin.com>
Hi,
On Tue, May 27, 2025 at 11:37:33AM +0200, Mathieu Dubois-Briand wrote:
> On Tue May 27, 2025 at 10:54 AM CEST, Mikko Rapeli wrote:
> > On Tue, May 27, 2025 at 09:43:02AM +0200, Mathieu Dubois-Briand wrote:
> >> On Tue May 27, 2025 at 9:17 AM CEST, Mikko Rapeli wrote:
> >> > On Tue, May 27, 2025 at 08:34:52AM +0200, Mathieu Dubois-Briand wrote:
> >> >> On Mon May 26, 2025 at 10:45 AM CEST, Mikko Rapeli wrote:
> >> >> > On Fri, May 23, 2025 at 05:16:58PM +0300, Mikko Rapeli via lists.openembedded.org wrote:
> >> >> >
> >> >> > I reviewed the runqemu and qemu-system-aarch64 arguments but could not see major differences.
> >> >> > One difference is that autobuilder runs with tap and I with slirp networking, but that
> >> >> > should not affect rootfs/ESP partition detection in u-boot. I've sent out v4 now.
> >> >> > If this still fails on autobuilder, then I'd need know what config fragments
> >> >> > are applied. I've configured qemuarm64 and genericarm64 with
> >> >> > ". oe-init-build-env" and then added TEST_RUNQEMUPARAMS += "slirp"
> >> >> > and SANITY_TESTED_DISTROS = "" to conf/local.conf. Maybe autobuilder
> >> >> > scripts add something more.
> >> >> >
> >> >> > Cheers,
> >> >> >
> >> >> > -Mikko
> >> >>
> >> >> Hi Mikko,
> >> >>
> >> >> Thanks for the new version, but I confirm it still fails.
> >> >>
> >> >> https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/1772
> >> >
> >> > Is it possible to grab the full boot log
> >> > /srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-1032659/tmp/work/qemuarm64-poky-linux/core-image-minimal/1.0/testimage/qemu_boot_log.20250526163143 ?
> >> >
> >> > It was referred in
> >> > https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/2499407/raw_inline
> >> >
> >>
> >> The file is gone :(
> >>
> >> I will launch a new build so I can capture the file.
> >
> > I finally reproduced this. The ESP partition is missing grub-efi
> > binaries and only config file is there. I have fixes pending for this
> > missing dependency on aarch64 and of course was building with them
> > in my tree. I will add a workaround to this test case and
> > try get to rebasing the fixes to wic...
> >
> > Cheers,
> >
> > -Mikko
>
> Oops, I replied before I saw your own reply. Thanks for the update!
No worries, it's good to see the confirmation that issues are the same.
Maybe these files could be captured fully from autobuilder in case there
are failures?
Like in this case, it's a race condition which is not so easy to reproduce.
Cheers,
-Mikko
next prev parent reply other threads:[~2025-05-27 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 13:41 [PATCH v3 1/3] u-boot: disable CONFIG_BLOBLIST on genericarm64 and qemuarm64 Mikko Rapeli
2025-05-22 13:41 ` [PATCH 2/3] qemuarm64.conf: allow overriding QB_OPT_APPEND Mikko Rapeli
2025-05-22 13:41 ` [PATCH 3/3] oeqa selftest uboot.py: add qemu KVM test case Mikko Rapeli
2025-05-23 13:15 ` [OE-core] " Mathieu Dubois-Briand
2025-05-23 14:16 ` Mikko Rapeli
[not found] ` <18422DAC420B1606.3062@lists.openembedded.org>
2025-05-26 8:45 ` Mikko Rapeli
2025-05-27 6:34 ` Mathieu Dubois-Briand
2025-05-27 7:17 ` Mikko Rapeli
2025-05-27 7:43 ` Mathieu Dubois-Briand
2025-05-27 8:54 ` Mikko Rapeli
2025-05-27 9:37 ` Mathieu Dubois-Briand
2025-05-27 9:55 ` Mikko Rapeli [this message]
2025-05-27 9:36 ` Mathieu Dubois-Briand
2025-05-27 9:52 ` Mikko Rapeli
[not found] ` <1841DD2A7A0AA7E1.3062@lists.openembedded.org>
2025-05-23 9:42 ` Mikko Rapeli
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=aDWMA7d77g-JX4p4@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=mathieu.dubois-briand@bootlin.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.