On Mon, 6 Nov 2023 at 13:48, Richard Purdie <richard.pur...@linuxfoundation.org> wrote:
> This highlights two issues: > > a) Why is the single sstate siginfo file gone? The most likely > explanation is that it wasn't accessed recently and was deleted by the > cleanup/ageing code. This makes sense since the code in question never > downloads it, only checks it exists and uses that as a marker. Our > usage "accesses" are in a different codepath to the parsing check. > > b) This means -S printdiff doesn't quite do what you'd expect since it > doesn't skip "covered" tasks in the same way a normal build would. > > To reproduce the test failure you should be able to just delete that > siginfo file from your local sstate. It is tempting to then not use the 'live' AB cache, and run the tests against private synthetic cache like the most of the rest of sstatetests does. Should we? Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#190213): https://lists.openembedded.org/g/openembedded-core/message/190213 Mute This Topic: https://lists.openembedded.org/mt/102197154/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
