Recent issues with BB_DONT_CACHE?
Over in the OpenBMC project, we rebased on yocto master (https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/37488). After this we started seeing intermittent issues with our os-release.bb recipe. We have a .bbappend in our meta-phosphor layer (https://github.com/openbmc/openbmc/blob/583147ea45f94ee363e9ae30ccb65b9ed1561b54/meta-phosphor/recipes-core/os-release/os-release.bbappend) that issues git commands to use the git hash to fill in our os-release.
After updating to the latest poky, sometimes the build works fine, other times we run into https://github.com/openbmc/openbmc/issues/3720
After some debug, it appears as if occasionally, bitbake is using the sstate cached os-release initially, and then during the build process it moves to using the correct hash id. This then causes the above error. We had issues with this way back in the day when we first introduced this bbappend and the solution was to add this to that recipe:
BB_DONT_CACHE = "1"