Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] ovmf-native: remove .pyc files from install
Date: Mon, 14 Oct 2024 14:39:15 +0300	[thread overview]
Message-ID: <Zw0C45RZmAqiS06R@nuoska> (raw)
In-Reply-To: <CANNYZj8vi7A_BSLTewb_LNLnPxzrmhn5fpxG8_OeOA_k-AhoXQ@mail.gmail.com>

Hi,

On Mon, Oct 14, 2024 at 01:28:07PM +0200, Alexander Kanavin wrote:
> On Mon, 14 Oct 2024 at 13:21, Mikko Rapeli <mikko.rapeli@linaro.org> wrote:
> > I don't know. At this point I'd rather remove all tests in uki
> > support which are causing so many issues.
> >
> > I tried to dig deeper into ovmf native but it looks like a mess.
> > meta-arm edk2 doesn't compile anything for native but just installs
> > the python scripts and gets away with it. Same did not work for ovmf.
> 
> The tests are important.
>
> Were you able to reproduce the issue locally? Ovmf is an awful
> component and a headache to work with, but I could take a look if I
> can get the same error. I'm just worried that deleting .pyc will only
> trigger the same error for the essential installed items.

No, I'm not able to reproduce the problem. Maybe I'd need to share the sstate
to another machine or user to trigger this. Just changing build paths
doesn't trigger the problem on my build machine.

Alternatively I can remove all x86/ovmf using tests and make things
work with u-boot firmware and aarch64, but then I need to test both
qemuarm64 and genericarm64 since details differ between them.

Cheers,

-Mikko


  reply	other threads:[~2024-10-14 11:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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

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=Zw0C45RZmAqiS06R@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=alex.kanavin@gmail.com \
    --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