On Thu, 9 Mar 2023 at 13:03, Richard Purdie <[email protected]> wrote:
> This is a wider problem, the sysroots are often modified when things > are running against it as we don't require task serialisation. Instead > the code tries to be careful about it's manipulations. Things aren't > always installed/removed just from that task either, it can happen with > *any* task that tries to extend the sysroot (which fetch, unpack and > patch do as well). Right, then I'm not sure what to do here (short of 'task-specific sysroots' :-D We can lessen the chances by serializing prepare_recipe_sysroot into fetch/unpack/patch/configure sequence. But it would not eliminate the possibility of other tasks stepping on those or each other. We can also make sysroot (de)population code more careful. But it won't solve the non-determinism. Making git wrapper run with python from hosttools/ solves a specific issue I saw, but not the broader problem. It happened just once, so it does seem exceedingly rare. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#178222): https://lists.openembedded.org/g/openembedded-core/message/178222 Mute This Topic: https://lists.openembedded.org/mt/97493237/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
