From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v8 0/8] systemd uki support
Date: Thu, 17 Oct 2024 11:52:08 +0300 [thread overview]
Message-ID: <ZxDQOGCEpAt7wnnt@nuoska> (raw)
In-Reply-To: <17FE9C82DB831F81.27606@lists.openembedded.org>
Hi,
On Tue, Oct 15, 2024 at 02:23:07PM +0300, Mikko Rapeli via lists.openembedded.org wrote:
> Hi,
>
> On Tue, Oct 15, 2024 at 11:43:33AM +0100, Richard Purdie wrote:
> > The arm test still fails:
> >
> > https://valkyrie.yoctoproject.org/#/builders/23/builds/267/steps/14/logs/stdio
> >
> > The traceback is at least cleaner now I fixed the lock error. I did
> > test with KVM disabled.
>
> Bugger. I had tested this on qemuarm64 and genericarm64 on an x86_64
> build host with Ubuntu 22.04. Is this an arm64 build host with Ubuntu 20.04?
>
> I will remove the tests as it is clearly too hard to get these running.
>
> It is a bit hard to figure out in which environments selftests are running.
I sent out a v9 which disables the test on non-x86_64 build hosts.
I hope that was the only failure seen from this series.
Cheers,
-Mikko
next prev parent reply other threads:[~2024-10-17 8:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 12:20 [PATCH v8 0/8] systemd uki support Mikko Rapeli
2024-10-11 12:20 ` [PATCH v8 1/8] uki.bbclass: add class for building Unified Kernel Images (UKI) Mikko Rapeli
2024-10-11 12:20 ` [PATCH v8 2/8] wic bootimg-efi.py: keep timestamps and add debug prints Mikko Rapeli
2024-10-11 12:20 ` [PATCH v8 3/8] wic bootimg-efi.py: change UKI support from wic plugin to uki.bbclass Mikko Rapeli
2024-10-11 12:20 ` [PATCH v8 4/8] oeqa selftest uki.py: add tests for uki.bbclass Mikko Rapeli
2024-10-11 12:20 ` [PATCH v8 5/8] oeqa selftest efibootpartition.py: add TEST_RUNQEMUPARAMS to runqemu Mikko Rapeli
2024-10-11 12:20 ` [PATCH v8 6/8] oeqa selftest efibootpartition.py: remove systemd-boot from grub-efi test Mikko Rapeli
2024-10-11 12:20 ` [PATCH v8 7/8] oeqa selftest wic.py: add TEST_RUNQEMUPARAMS to runqemu Mikko Rapeli
2024-10-11 12:20 ` [PATCH v8 8/8] oeqa selftest wic.py: support UKIs via uki.bbclass Mikko Rapeli
2024-10-13 7:43 ` [OE-core] [PATCH v8 0/8] systemd uki support Richard Purdie
2024-10-14 10:30 ` Mikko Rapeli
2024-10-14 12:13 ` Mikko Rapeli
[not found] ` <17FE4B15CF045259.4702@lists.openembedded.org>
2024-10-15 6:44 ` Mikko Rapeli
2024-10-15 9:45 ` Richard Purdie
2024-10-15 10:43 ` Richard Purdie
2024-10-15 11:23 ` Mikko Rapeli
2024-10-15 11:32 ` Alexander Kanavin
[not found] ` <17FE9D06966A2DE5.32376@lists.openembedded.org>
2024-10-15 11:36 ` Alexander Kanavin
2024-10-15 14:13 ` Richard Purdie
2024-10-15 14:23 ` Mikko Rapeli
[not found] ` <17FE9C82DB831F81.27606@lists.openembedded.org>
2024-10-17 8:52 ` Mikko Rapeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-14 10:28 [PATCH] ovmf-native: remove .pyc files from install Mikko Rapeli
2024-10-14 11:05 ` [OE-core] " Alexander Kanavin
2024-10-14 11:21 ` Mikko Rapeli
2024-10-14 11:28 ` Alexander Kanavin
2024-10-14 11:39 ` Mikko Rapeli
2024-10-14 11:42 ` Alexander Kanavin
2024-10-14 12:01 ` Richard Purdie
2024-10-14 12:34 ` Ross Burton
2024-10-14 12:52 ` Richard Purdie
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=ZxDQOGCEpAt7wnnt@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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