Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mikko.rapeli@linaro.org, Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v9 00/11] systemd uki support
Date: Tue, 22 Oct 2024 20:54:42 +0100	[thread overview]
Message-ID: <1f3e21110ad79efab2bb46a4ef779355a9ae7458.camel@linuxfoundation.org> (raw)
In-Reply-To: <Zxf-KtENbXFeTMTp@nuoska>

On Tue, 2024-10-22 at 22:34 +0300, Mikko Rapeli via lists.openembedded.org wrote:
> Hi,
> 
> On Tue, Oct 22, 2024 at 10:26:52AM +0000, Ross Burton wrote:
> > On 17 Oct 2024, at 09:45, Mikko Rapeli via lists.openembedded.org <mikko.rapeli=linaro.org@lists.openembedded.org> wrote:
> > > v9: Fixed unrelated ext4 rawcopy wic test on genericarm64. Enabled new aarch64 target
> > >    wic test on x86_64 build host only since boot with qemu is currently
> > >    failing on aarch64 build host.
> > 
> > Sorry, but I don’t think disabling tests based on the build machine is the right thing to do here.
> 
> Well I'm running out of options to try.
> 
> > My gut reaction is that there is another test that is running with kvm enabled, thus breaking uboot.  I’ll do a build on my own machine shortly and see if I can replicate.
> 
> IMO this is a generic problem. The selftest code is not fully in control of
> the bitbake build config, including runqemu. Snippets get enabled here and
> there. Difficult to know what the effective config in CI is. This also not visible
> in the AB build logs, or at least I could not find it.
> 
> Thanks for helping, I hope you can reproduce this.

Ross asked for a failing build log, there is one here:

https://valkyrie.yoctoproject.org/#/builders/23/builds/306/steps/14/logs/stdio

and the config for this is clearly visible here in the step before it:

https://valkyrie.yoctoproject.org/#/builders/23/builds/306/steps/13/logs/stdio

There isn't anything more being set or any other magic, that is the
config and it runs an oe-selftest command (the one at the top of the
first link above).

Cheers,

Richard


      reply	other threads:[~2024-10-22 19:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  8:45 [PATCH v9 00/11] systemd uki support Mikko Rapeli
2024-10-17  8:45 ` [PATCH v9 01/11] uki.bbclass: add class for building Unified Kernel Images (UKI) Mikko Rapeli
2024-10-17  8:45 ` [PATCH v9 02/11] wic bootimg-efi.py: keep timestamps and add debug prints Mikko Rapeli
2024-10-17  8:45 ` [PATCH v9 03/11] wic bootimg-efi.py: change UKI support from wic plugin to uki.bbclass Mikko Rapeli
2024-10-17  8:45 ` [PATCH v9 04/11] oeqa selftest uki.py: add tests for uki.bbclass Mikko Rapeli
2024-10-17  8:45 ` [PATCH v9 05/11] oeqa selftest efibootpartition.py: add TEST_RUNQEMUPARAMS to runqemu Mikko Rapeli
2024-10-17  8:45 ` [PATCH v9 06/11] oeqa selftest efibootpartition.py: remove systemd-boot from grub-efi test Mikko Rapeli
2024-10-17  8:45 ` [PATCH v9 07/11] oeqa selftest wic.py: add TEST_RUNQEMUPARAMS to runqemu Mikko Rapeli
2024-10-17  8:45 ` [PATCH v9 08/11] oeqa selftest wic.py: support UKIs via uki.bbclass Mikko Rapeli
2024-10-17  8:45 ` [PATCH v9 09/11] oeqa data.py: add skipIfNotBuildArch decorator Mikko Rapeli
2024-10-17  8:45 ` [PATCH v9 10/11] oeqa selftest wic.py: mark efi tests to run on x86_64 build host only Mikko Rapeli
2024-10-17  8:45 ` [PATCH v9 11/11] oeqa selftest wic.py: fix missing ext4 image Mikko Rapeli
2024-10-22 10:26 ` [OE-core] [PATCH v9 00/11] systemd uki support Ross Burton
2024-10-22 19:34   ` Mikko Rapeli
2024-10-22 19:54     ` Richard Purdie [this message]

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=1f3e21110ad79efab2bb46a4ef779355a9ae7458.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Ross.Burton@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox