> > That is a big clue in itself, that function was added for a reason. The > reason that code was added may be related to the problem. > > https://git.openembedded.org/bitbake/commit/?id=5293a1b36eeb89f57577cb709ec7f293909039a1 > > > > >> >> >>> I don't understand how you have two siginfo files with different sigs >>> and the same data. >> >> It's a mystery to me too at this point! Is there anything I can do to >> get more information on how it's calculating the task hash? >> >> I'll try and run across more PCs as well to see if it's just the one >> CI machine that's different. > > I'd try adding the above commit as there were bugs in this area that > sound very similar to this. > > >
I've patched my siggen.py manually with changes from both the linked patches. I'm rebuilding now but it has understandably changed the sigs of a while bunch of tasks so I'll need to repopulate the caches and see if it's the same across build machines which will take a while! The changes to siggen.py between langdale and scarthgap look pretty extensive - Is there a chance they'll be contained to siggen.py enough that I can lift the scarthgap version wholesale? Or is it likely to break when paired with an older bitbake checkout? Thanks, Phil
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63942): https://lists.yoctoproject.org/g/yocto/message/63942 Mute This Topic: https://lists.yoctoproject.org/mt/108814179/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
