You didn't say which Yocto release that WRL build was using, maybe your deploy artifacts are changing due to package_get_auto_pr calls or not excluded DATETIME in your filenames as described in: https://patchwork.yoctoproject.org/project/oe-core/patch/932d980fb4fcfd3b78183d5bd51adb4f038eee47.1700600804.git.martin.ja...@gmail.com/
unfortunately this whole series https://patchwork.yoctoproject.org/project/oe-core/list/?series=19541 was rejected: https://lists.openembedded.org/g/openembedded-core/message/191101 On Wed, Dec 13, 2023 at 4:54 PM Robert P. J. Day <rpj...@crashcourse.ca> wrote: > > i *know* i should know the answer to this, but someone just showed > me a build (WRLinux-based, but still relevant) where the linux kernel > recipe uses: > > SRCREV_machine = ${AUTOREV} > > which is what one reads in the WRL version of linux-yocto-custom.bb, > but also makes it clear in that recipe file that that is discouraged. > > in any event, this appears to be forcing an entire rebuild of the > kernel every time, even in the presence of sstate-cache, so the > obvious question is, what is it about using ${AUTOREV} that defeats > the use of sstate-cache? apologies if this should be obvious. > > rday > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#192308): https://lists.openembedded.org/g/openembedded-core/message/192308 Mute This Topic: https://lists.openembedded.org/mt/103151800/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
