All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Mikko Rapeli" <mikko.rapeli@linaro.org>
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 11:36:10 +0200	[thread overview]
Message-ID: <DA6UARJCKY1F.22D63SXC39NBQ@bootlin.com> (raw)
In-Reply-To: <DA6RW4W11Z6L.1MNI997UJXXB5@bootlin.com>


[-- Attachment #1.1: Type: text/plain, Size: 2343 bytes --]

On Tue May 27, 2025 at 9:43 AM CEST, Mathieu Dubois-Briand wrote:
> On Tue May 27, 2025 at 9:17 AM CEST, Mikko Rapeli wrote:
>> Hi,
>>
>> 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.

New build. There is also a failure on bitbake selftest here, but it
seems to be an unrelated intermittent issue.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/1778

I believe the file you are looking for is
/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-932426/tmp/work/qemuarm64-poky-linux/core-image-minimal/1.0/testimage/qemu_boot_log.20250527082811.2,
I'm attaching it to my mail. But I'm not sure there is more data than
what you already had.

I will try to backup the whole build directory once the build is done,
in the case you need some other file.

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


[-- Attachment #2: qemu_boot_log.20250527082811.2 --]
[-- Type: application/octet-stream, Size: 1733 bytes --]

  parent reply	other threads:[~2025-05-27  9:36 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
2025-05-27  9:36               ` Mathieu Dubois-Briand [this message]
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=DA6UARJCKY1F.22D63SXC39NBQ@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=mikko.rapeli@linaro.org \
    --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.