Fix weird rebuild issue even when sstate signature doesn't change
Get series with b4
b4 am '[email protected]'Versions newest first
- v1 Latest0 of 1 patch 13 repliesIn review
Patches in v1 No applies recorded yet
The patch the cover letter announces is not in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1] Fix weird rebuild issue even when sstate signature doesn't change
This patch is to fix one weird issue I've keeping seeing recently when using sstate. Even with a minimal build, there're around 50 recipes rebuilt from scratch even though sstate packages in sstate_cache do match. Actually the end result is to just overwrite sstate packages again with same sigature for those recipes.
https://lists.yoctoproject.org/pipermail/poky/2010-December/001063.html
The cause for this mess is from misinterpretation of the index of a list, which then points to wrong setscene tasks instead of desired ones. The end result is that some tasks which don't need execution are scheduled while other setscene tasks which need run are simply skipped.
It's based on Paul's sstate branch.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: tk/sstate
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=tk/sstate
Thanks,
Kevin Tian <[email protected]>
---
Kevin Tian (1):
runqueue.py: use correct task ID when checking validity of setscene
tasks
bitbake/lib/bb/runqueue.py | 16 +++++++++++----- 1 files changed, 11 insertions(+), 5 deletions(-)