<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Yep, tasks that were looked up, and actual filenames attempted.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br>Alex</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 20, 2014 at 4:06 PM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Thu, 2014-02-20 at 15:41 +0000, Damian, Alexandru wrote:<br>
> I would think against it, because<br>
<br>
> - it's very inefficient to send a Skipped event for each missed task<br>
> than to collect all the data and send it in one shot<br>
> - it's faster to send the event from the sstate.bbclass than to return<br>
> the task ids and then call again a python function to generate the<br>
> sstate file names - basically replicating the sstate.bbclass code in<br>
> bitbake<br>
> - the queueTaskSkipped event has a different semantic than what we<br>
> need here to return a whole batch of data; creating a new event type<br>
> from scratch is a bit pointless since the inheritance would need to be<br>
> broken<br>
> - knotty can receive MetadataEvents just as well as sceneTaskSkipped<br>
> event, or any variation of it<br>
<br>
</div>I guess I'd like to understand which information from this even you're<br>
particularly interested in?<br>
<br>
Do I understand correctly that you want the actual filenames attempted?<br>
<br>
Cheers,<br>
<br>
Richard<br>
<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Alex Damian<div>Yocto Project<br></div><div>SSG / OTCÂ </div></div>
</div>