scarthgap runtime SPDX error
Nevermind... I see the patch right below this that looks like it might fix it. I'll test the patch series out and see if it works.
Quoted 25 lines · Ryan Eatmon via lists.openembedded.org
We started seeing a new error on scarthgap on Friday.
ERROR: No runtime SPDX document found for bt-enable, False sstate:bt-enable:all-oe-linux:1.0:r1:allarch:12: sstate:bt-enable::1.0:r1::12:
The package it is referring to changes from image to image and run to run, but we only get a single error message.
If I do a build not using the sstate-cache, the build works fine. If I then update our shared sstate-cache with those rebuilt files and run a second build using the cache, the error comes back.
I don't see anything obvious in the two bitbake commits and handful on oe-core. I've spent all day today trying to do the two step process to see if I can find the commit that causes this.
Has anyone else seen anything like this in your scarthgap builds starting Friday?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#202562): https://lists.openembedded.org/g/openembedded-core/message/202562
Mute This Topic: https://lists.openembedded.org/mt/107585320/6551054
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Signature · 3 lines
Ryan Eatmon [email protected] ----------------------------------------- Texas Instruments, Inc. - LCPD - MGTS
It does. Please accept that patch series onto scarthgap ASAP.
Quoted 35 lines · Ryan Eatmon via lists.openembedded.org
Nevermind... I see the patch right below this that looks like it might fix it. I'll test the patch series out and see if it works.
Quoted 5 lines · Ryan Eatmon via lists.openembedded.org
We started seeing a new error on scarthgap on Friday.
ERROR: No runtime SPDX document found for bt-enable, False sstate:bt-enable:all-oe-linux:1.0:r1:allarch:12: sstate:bt-enable::1.0:r1::12:
Quoted 14 lines
The package it is referring to changes from image to image and run to run, but we only get a single error message.
If I do a build not using the sstate-cache, the build works fine. If I then update our shared sstate-cache with those rebuilt files and run a second build using the cache, the error comes back.
I don't see anything obvious in the two bitbake commits and handful on oe-core. I've spent all day today trying to do the two step process to see if I can find the commit that causes this.
Has anyone else seen anything like this in your scarthgap builds starting Friday?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#202563): https://lists.openembedded.org/g/openembedded-core/message/202563
Mute This Topic: https://lists.openembedded.org/mt/107585320/6551054
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Signature · 3 lines
Ryan Eatmon [email protected] ----------------------------------------- Texas Instruments, Inc. - LCPD - MGTS