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

[Tian, Kevin]

>From: Gary Thomas [mailto:gary at mlbassoc.com]
>Sent: Thursday, December 16, 2010 12:10 AM
>
>On 12/15/2010 02:12 AM, Richard Purdie wrote:
>> 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!
>
>Mucho bettero (TM) :-)
>
>I just tried this from master and at least on the same machine
>but different build paths, it performed much as hoped.  My initial
>build (step 1) took some 165 minutes, building the same target using
>the sstate cache from step 1 took only 22.  The only packages rebuilt
>during step 2 were the kernel and the image tasks (I tested this with
>my own image+kernel recipes, so it's OK if this differs a little from
>other's results).

Good to see that. :-)

Thanks
Kevin