Re: [OE-core] [PATCH v8 0/8] systemd uki support

[Mikko Rapeli <mikko.rapeli@linaro.org>]

Hi,

On Mon, Oct 14, 2024 at 01:42:46PM +0200, Alexander Kanavin wrote:
> On Mon, 14 Oct 2024 at 13:39, Mikko Rapeli <mikko.rapeli@linaro.org> wrote:
> > 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.
> 
> Can I see the link to the autobuilder failure where this was observed?

Yes:

On Sun, Oct 13, 2024 at 08:43:15AM +0100, Richard Purdie wrote:
> I'm still seeing failures in CI:
> 
> https://valkyrie.yoctoproject.org//#/builders/23/builds/249/steps/14/logs/stdio
> 
> which is despite setting:
> 
> https://git.yoctoproject.org/poky/commit/?h=master-next&id=6211ad9210e82a5a8dd157c63752ad332c2f5de6
> 
> QEMU_USE_KVM = "False"
> 
> into the test to ensure it doesn't have the issue the barebox testing
> was seeing.
> 
> I've sent a patch to try and clean up the lock error.
> 
> There is also this:
> 
> https://valkyrie.yoctoproject.org//#/builders/76/builds/235
> https://valkyrie.yoctoproject.org//#/builders/48/builds/181
> https://valkyrie.yoctoproject.org//#/builders/54/builds/230
> 
> which is due to the binaries being run "in tree" within the edk2 build
> as well as from the sysroot. This generates two sets of pyc files which
> then conflict (or not) depending on which host the build ran on and
> which pyc files are in sstate.
> 
> We're going to have to get this fixed before it can merge, probably by
> deleting the pyc files at install unless we can find anything more
> elegant.

After few experiments failed, I went with this.

Cheers,

-Mikko