<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 30, 2013 at 9:18 AM, Chris Larson <span dir="ltr"><<a href="mailto:clarson@kergoth.com" target="_blank">clarson@kergoth.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Sat, Dec 28, 2013 at 6:24 AM, Martin Jansa <span dir="ltr"><<a href="mailto:martin.jansa@gmail.com" target="_blank">martin.jansa@gmail.com</a>></span> wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Wed, Dec 18, 2013 at 04:21:27PM +0000, Richard Purdie wrote:<br>
> Its useful to understand where the delta starts against an existing sstate cache<br>
> for a given target. Adding this to the output of the -S option seems like a<br>
> natural fit.<br>
><br>
> We use the hashvalidate function to figure this <span><span class="il">out</span></span> and assume it can find siginfo<br>
> files for more than just the setscene tasks.<br>
<br>
</div>I haven't tried to find smaller reproducer or exact part of code where<br>
it happends, but in bigger builds I have it fails with<br>
<br>
I'll try to reproduce and narrow it a bit, but if you have tip where<br>
to look first..<br>
<br>
<span><span class="il">IndexError</span></span>: <span><span class="il">list</span></span> <span><span class="il">index</span></span> <span><span class="il">out</span></span> of <span><span class="il">range</span></span>:</blockquote>
</div><br></div>I’m hitting this now as well.</blockquote></div><br>To clarify further, I’m hitting this with stock poky master, qemux86, bitbake -S core-image-base.</div><div class="gmail_extra"><br></div><div class="gmail_extra">
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?<br>
-- <br>Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics
</div></div>