On 12/21/24 00:09, Mathieu Dubois-Briand wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
Hi Hongxu,
I'm back on this issue. So yesterday I tried again to pick these
patches, and got warnings again:
https://valkyrie.yoctoproject.org/#/builders/29/builds/682
If I relaunch the builds, sometimes they will success, sometimes I still
get the warnings. Something seems to be intermittent here.
I tried to reproduce locally, and again, I get the warnings in some
intermittent way.
My setup was:
- Clean build directory, empty sstate cache.
- The local.conf attached. This is mainly the configuration used for
https://valkyrie.yoctoproject.org/#/builders/8/builds/698, with some
minor changes (like disabling the shared sstate configuration).
- Using meta, meta-poky and meta-yocto-bsp at this revision:
https://git.yoctoproject.org/poky-ci-archive/tag/?h=a-full-685
- Used: bitbake core-image-sato core-image-sato-sdk core-image-minimal
core-image-minimal-dev core-image-full-cmdline core-image-sato:do_populate_sdk
Now here is how it went:
- On my very first build, I got some SPDX warnings.
- On my next build they were all gone.
- I tried to tweak a bit my config, cleaned my cache again and still got
no warnings.
- Then after some various modifications, I switched back again to my
very first configuration, and got again some SPDX warnings.
So I'm sorry, I cannot give you some exact instructions to reproduce
this issue, but still we have some intermittent warnings :(
Hi Mathieu,
Thanks for the information you provided, it helps me to reproduce two issues
1. While hosts with different archs (such as x86-64, aarch64) sharing
same sstate cache, build image from existed sstate cache reported
SPDX ID missing warnings. Here is steps:
On x86-64 host, build image core-image-minimal for qemuarm64
$ echo 'MACHINE = "qemuarm64"' >> conf/local.conf
$ bitbake core-image-sato
On aarch64 host, sharing above sstate cache and build image
core-image-minimal for qemuarm64
$ echo 'MACHINE = "qemuarm64"' >> conf/local.conf
$ bitbake core-image-sato
2. Sharing same sstate cache for different machines
$ echo 'MACHINE = "qemux86-64"' >> conf/local.conf
$ bitbake core-image-minimal
$ echo 'MACHINE = "qemuarm64"' >> conf/local.conf
$ bitbake core-image-minimal
The issue was caused by the following two patches,
[OE-core] [PATCH 2/4] meta/lib/oe/spdx30_tasks.py: fix hash link
conflict while multiconfig enabled
[OE-core] [PATCH V2 3/4] gcc-cross.inc: add var-SSTATE_ARCHS_TUNEPKG to
vardeps of do_create_spdx
I will resend review and drop them
//Hongxu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#209068):
https://lists.openembedded.org/g/openembedded-core/message/209068
Mute This Topic: https://lists.openembedded.org/mt/110158019/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
