They're forbidden in selftests as a whole, for other reasons. You can probably find the reasons out via git blame.
Alex On Fri, 26 Jan 2024 at 16:14, Joakim Tjernlund <joakim.tjernl...@infinera.com> wrote: > > On Fri, 2024-01-26 at 15:55 +0100, Alexander Kanavin wrote: > > On Fri, 26 Jan 2024 at 15:52, Joakim Tjernlund > > <joakim.tjernl...@infinera.com> wrote: > > > A thought just occurred to me, these vars(SANITY_TESTED_DISTROS, > > > buildhistory etc.), > > > do they need to be off in the original machine when building up the > > > SSTATE ? > > > I figured they just needed to be off for the repro build(in xxxx-st dir) > > > but > > > now I am not sure any more. > > > > Machine is typically understood as MACHINE setting, please do not > > confuse it with a build from a specific configuration in build/conf/. > > > > SANITY_TESTED_DISTROS and buildhistory do not factor in sstate > > signature calculation, so turning them off and one will not cause > > cache invalidation and a rebuild. > > > > Alex > > A bit odd that repro. builds forbids them if they don't factor in sstate > > Jocke
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#194391): https://lists.openembedded.org/g/openembedded-core/message/194391 Mute This Topic: https://lists.openembedded.org/mt/103973969/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
