| Summary: | Python library code changes don't cause rebuild, and trigger taskhash mismatch | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Joshua Watt <JPEWhacker> |
| Component: | bitbake | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | poky.bs.watcher, poky.watcher, randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 5.2 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Joshua Watt
2025-03-12 18:24:28 UTC
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. |