On Wed, 18 Oct 2023 at 21:39, Alexandre Belloni <[email protected]> wrote: > ERROR: Can't find a task we're supposed to have written out? (hash: > e79d70b9c2cc72030c1ce822525510699a1eeb1ddf5986271d3217422244366a)? > ERROR: Can't find a task we're supposed to have written out? (hash: > 999250461834bf74545962a8577bc26854a3d08bb2a96140d5efe314e0ef2d63)?
This is proving tricky to reproduce. It happens fairly reliably in oe-selftest-armhost, but so far never on regular oe-selftest, or in standalone local build on an arm host where I run only the selftests that are failing. It seems like one of those dreaded selftest things that fail only in particular execution order with other tests. The only idea I have right now is to run specially configured oe-selftest-armhost which would run only a subset (e.g. just sstatetests) and see if it can be narrowed down from there. I'm also tempted to set this aside for now as it has all the signs of protracted, painful debugging slog, and push the esdk/sstate build registry subject, so there's something to show for it soon. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#189527): https://lists.openembedded.org/g/openembedded-core/message/189527 Mute This Topic: https://lists.openembedded.org/mt/102035446/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
