public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: u-boot@lists.denx.de, trini@konsulko.com, sjg@chromium.org,
	ilias.apalodimas@linaro.org
Subject: Re: [PATCH v4 2/4] efi_loader: rename BOOTEFI_BOOTMGR to EFI_BOOTMGR
Date: Mon, 15 Jan 2024 19:12:47 +0900	[thread overview]
Message-ID: <ZaUFH3r9MdW+tHTv@octopus> (raw)
In-Reply-To: <d70d5134-1cc9-4d56-9aa3-499ed992584c@gmx.de>

On Mon, Jan 15, 2024 at 09:34:51AM +0100, Heinrich Schuchardt wrote:
> On 1/15/24 01:58, AKASHI Takahiro wrote:
> > On Sun, Jan 14, 2024 at 01:46:45PM +0100, Heinrich Schuchardt wrote:
> > > On 1/10/24 02:16, AKASHI Takahiro wrote:
> > > > At this point, EFI boot manager interfaces is fully independent from
> > > > bootefi command. So just rename the configuration parameter.
> > > > 
> > > > Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> > > > Reviewed-by: Simon Glass <sjg@chromium.org>
> > > 
> > > This patch breaks the 'bootefi hello' command in
> > > qemu-riscv64_smode_defconfig and other QEMU defconfigs.
> > 
> > What happened? Please elaborate details so that I can trace your issue.
> > 
> > On my side, I didn't see any problem with "bootefi hello" on qemu-arm64
> > and moreover CI check (github pull request) didn't complain anything.
> 
> The failures are logged in
> https://source.denx.de/u-boot/custodians/u-boot-efi/-/pipelines/19302

In the logs for qemu-arm64, qemu-risc64 and maybe others as well,
I see the same error:
--- ---
______________________________ test_efi_grub_net _______________________________
test/py/tests/test_efi_loader.py:188: in test_efi_grub_net
    addr = fetch_tftp_file(u_boot_console, 'env__efi_loader_grub_file')
test/py/tests/test_efi_loader.py:136: in fetch_tftp_file
    assert expected_text in output
E   assert 'Bytes transferred = 520192' in "*** ERROR: `serverip' not set"
--- ---

This seems to be the root cause and my commit will have nothing to do
with the problem.
Please check the test environment.

-Takahiro Akashi

> I have pushed the tag failed_20240114 to
> https://source.denx.de/u-boot/custodians/u-boot-efi.git for analysis.
> 
> Best regards
> 
> Heinrich

  reply	other threads:[~2024-01-15 10:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10  1:16 [PATCH v4 0/4] cmd: bootefi: refactor the code for bootmgr AKASHI Takahiro
2024-01-10  1:16 ` [PATCH v4 1/4] efi_loader: split unrelated code from efi_bootmgr.c AKASHI Takahiro
2024-01-10  1:16 ` [PATCH v4 2/4] efi_loader: rename BOOTEFI_BOOTMGR to EFI_BOOTMGR AKASHI Takahiro
2024-01-14 12:46   ` Heinrich Schuchardt
2024-01-15  0:58     ` AKASHI Takahiro
2024-01-15  8:34       ` Heinrich Schuchardt
2024-01-15 10:12         ` AKASHI Takahiro [this message]
2024-01-15 14:16           ` Heinrich Schuchardt
2024-01-16  1:43             ` AKASHI Takahiro
2024-01-16 18:44               ` Heinrich Schuchardt
2024-01-17  0:40                 ` AKASHI Takahiro
2024-01-10  1:16 ` [PATCH v4 3/4] net: tftp: remove explicit efi configuration dependency AKASHI Takahiro
2024-01-10  1:16 ` [PATCH v4 4/4] fs: " AKASHI Takahiro

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=ZaUFH3r9MdW+tHTv@octopus \
    --to=takahiro.akashi@linaro.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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