[poky] [PATCH 0/1] Fix weird rebuild issue even when sstate signature doesn't change

Tian, Kevin kevin.tian at intel.com
Wed Dec 15 03:12:55 PST 2010


>From: Richard Purdie [mailto:richard.purdie at linuxfoundation.org]
>Sent: Wednesday, December 15, 2010 5:12 PM
>
>On Tue, 2010-12-14 at 21:40 +0800, Kevin Tian wrote:
>> 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.
>
>I've merged this patch into master, good catch and hopefully this gets
>sstate into a good working state.
>
>I've merged an updated version of Paul's sstate branch too.
>
>I'm hoping this makes sstate packages finally usable!
>

I think now it's on much better shape. I tried minimal build with both same and different
source dir. Only three packages are out of the scope:
	linux-yocto
	task-poky-boot
	poky-image-minimal

poky-image-minimal is expected. task-poky-boot is caused by linux-yocto.do_deploy. The
reason why linux-yocto.do_deploy fails to match is because it depends on DATETIME.

However there's one issue preventing me to come up a fix, which will be sent out in a
separate thread for suggestion.

Thanks
Kevin


More information about the poky mailing list