[bitbake-devel] [PATCH] runqueue: Add output for -S option for listing the changepoints compared with an sstate cache

[Chris Larson]

On Mon, Dec 30, 2013 at 9:18 AM, Chris Larson <clarson at kergoth.com> wrote:

> On Sat, Dec 28, 2013 at 6:24 AM, Martin Jansa <martin.jansa at gmail.com>wrote:
>
>> On Wed, Dec 18, 2013 at 04:21:27PM +0000, Richard Purdie wrote:
>> > Its useful to understand where the delta starts against an existing
>> sstate cache
>> > for a given target. Adding this to the output of the -S option seems
>> like a
>> > natural fit.
>> >
>> > We use the hashvalidate function to figure this out and assume it can
>> find siginfo
>> > files for more than just the setscene tasks.
>>
>> I haven't tried to find smaller reproducer or exact part of code where
>> it happends, but in bigger builds I have it fails with
>>
>> I'll try to reproduce and narrow it a bit, but if you have tip where
>> to look first..
>>
>> IndexError: list index out of range:
>
>
> I’m hitting this now as well.


To clarify further, I’m hitting this with stock poky master, qemux86,
bitbake -S core-image-base.

Actually, this is getting in my way trying to do something I don’t want it
doing anyway. I want to dump the signature data from one config, and use
bitbake-whatchanged from another build. If I wanted to compare something
right here, I’d have run bitbake-whatchanged. This change confuses me a
bit. -S emits signature data, according to the bitbake help and the
semantics of the command. Are we trying to kill bitbake-whatchanged in
favor of making -S do both jobs, emit and compare?
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20131230/315fa974/attachment-0002.html>