There appears to be a problem where bitbake will not detect that changes are made to python library code and recalculate hashes appropriately. This not only means that tasks aren't rerun when they should be, but also that taskhash mismatches can easily occur. This appear to be easily reproduced with the following steps: $ bitbake core-image-minimal edit spdx30_tasks.py:create_spdx() by adding extra whitespace $ bitbake core-image-minimal Note that no tasks rerun, even though the task changed invalidate and run an upstream task with: $ bitbake -f --runall collect_spdx_deps core-image-minimal Many task hash mismatch errors will occur
You can see this a little faster with: bitbake core-image-minimal -c clean bitbake core-image-minimal -S none ls -1la tmp/stamps/qemux86_64-poky-linux/core-image-minimal/ <edit spdx30_tasks.py:create_spdx() by adding extra whitespace> bitbake core-image-minimal -S none ls -1la tmp/stamps/qemux86_64-poky-linux/core-image-minimal/ (shows the same as above) rm tmp/cache/ -rf bitbake core-image-minimal -S none ls -1la tmp/stamps/qemux86_64-poky-linux/core-image-minimal/ shows duplicate sigdata files with new hashes (do_build for example changes)
I think the problem is that whilst bitbake reparses it's configuration, we don't know when to reparse the recipes since we don't know which hashes of which functions make it into which recipes. This means we don't know whether to load a recipe's values from the cache or not.
Put another way, if the overall checksum of "lib" changes at all, we need to invalidate the cache and reparse everything
The issue is the base configuration hash doesn't account for the module dependencies. I've sent a patch.
https://git.yoctoproject.org/poky/commit/?id=6610cad12a062592956257961a790ec6a3012b8b