From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Tom Rini" <trini@konsulko.com>, "Fabio Estevam" <festevam@gmail.com>
Cc: <openembedded-core@lists.openembedded.org>,
"Quentin Schulz" <quentin.schulz@cherry.de>,
<adrian.freihofer@siemens.com>,
"Marek Vasut" <marek.vasut@mailbox.org>
Subject: Re: [OE-core] [PATCH] u-boot: upgrade 2025.04 -> 2025.07
Date: Wed, 09 Jul 2025 10:21:34 +0200 [thread overview]
Message-ID: <DB7DN2I98ZYX.3V9C86PS14M9B@bootlin.com> (raw)
In-Reply-To: <20250708175732.GU6424@bill-the-cat>
On Tue Jul 8, 2025 at 7:57 PM CEST, Tom Rini wrote:
> On Tue, Jul 08, 2025 at 02:04:15PM -0300, Fabio Estevam wrote:
>> Hi Mathieu,
>>
>> On Tue, Jul 8, 2025 at 9:37 AM Mathieu Dubois-Briand
>> <mathieu.dubois-briand@bootlin.com> wrote:
>> >
>> > On Tue Jul 8, 2025 at 3:29 AM CEST, Fabio Estevam via lists.openembedded.org wrote:
>> > > Upgrade to U-Boot 2025.07.
>> > >
>> > > Signed-off-by: Fabio Estevam <festevam@gmail.com>
>> > > ---
>> >
>> > Hi Fabio,
>> >
>> > Thanks for your patch.
>> >
>> > It looks like this is breaking selftests on the autobuilder:
>> >
>> > 2025-07-08 07:43:52,116 - oe-selftest - INFO - fitimage.UBootFitImageTests.test_sign_cascaded_uboot_fit_image (subunit.RemotedTestCase)
>> > 2025-07-08 07:43:52,118 - oe-selftest - INFO - ... FAIL
>> > ...
>> > ERROR: u-boot-1_2025.07-r0 do_compile: oe_runmake failed
>> > ...
>> > | arm-poky-linux-gnueabi-ld.bfd: cannot find arch/arm/lib/lib.a: No such file or directory
>> >
>> >
>> > Both on debian and armhost:
>> >
>> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/1923
>> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/2077
>> >
>> > Can you have a look at these failures please?
>>
>> Thanks for the report.
>>
>> I am adding some folks on CC in case they have some ideas.
>
> Interesting. How can we trigger that outside of the autobuilder?
Hi,
It's not so easy to reproduce, as it looks like it is somehow linked
with the host environment: this have been failing on debian workers but
not on the fedora ones.
So basic instructions are below, but this was not enough to reproduce it
in the ubuntu 24.4 docker I've been using so far.
git clone git://git.yoctoproject.org/poky-ci-archive -b autobuilder.yoctoproject.org/valkyrie/a-full-1972
cd poky-ci-archive
. oe-init-build-env
Add following lines in conf/local.conf (I bet only the last one is
really needed, but let's try to be as close as possible as the
autobuilder configuration):
MACHINE = "qemux86-64"
DISTRO = "poky"
SDKMACHINE = "x86_64"
PACKAGE_CLASSES = "package_rpm"
RPM_GPG_SIGN_CHUNK = '1'
IMAGE_INSTALL:append = ' ssh-pregen-hostkeys'
SANITY_TESTED_DISTROS = ''
Add poky-ci-archive/meta-selftest in conf/bblayers.conf.
And finally, run the tests:
oe-selftest -r fitimage.UBootFitImageTests.test_sign_cascaded_uboot_fit_image
oe-selftest -r fitimage.UBootFitImageTests.test_sign_standalone_uboot_atf_tee_fit_image
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-07-09 8:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 1:29 [PATCH] u-boot: upgrade 2025.04 -> 2025.07 Fabio Estevam
2025-07-08 12:37 ` [OE-core] " Mathieu Dubois-Briand
2025-07-08 17:04 ` Fabio Estevam
2025-07-08 17:57 ` Tom Rini
2025-07-09 8:21 ` Mathieu Dubois-Briand [this message]
2025-07-09 14:29 ` Tom Rini
2025-07-10 13:02 ` Mikko Rapeli
[not found] ` <1850E573A97965CE.21176@lists.openembedded.org>
2025-07-10 14:50 ` Mikko Rapeli
2025-07-10 14:59 ` Tom Rini
2025-07-10 14:44 ` [PATCH] scripts/Makefile.lib: fix *_efi.so dependency to PLATFORM_LIBGCC Mikko Rapeli
2025-07-10 15:08 ` Mikko Rapeli
2025-07-10 22:25 ` Tom Rini
2025-07-09 9:35 ` [OE-core] [PATCH] u-boot: upgrade 2025.04 -> 2025.07 Freihofer, Adrian
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=DB7DN2I98ZYX.3V9C86PS14M9B@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=adrian.freihofer@siemens.com \
--cc=festevam@gmail.com \
--cc=marek.vasut@mailbox.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=quentin.schulz@cherry.de \
--cc=trini@konsulko.com \
/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.