[Toaster] RFC: creating our own build logs

[Smith, Elliot]

On 21 October 2015 at 10:53, Smith, Elliot <elliot.smith at intel.com> wrote:

> On 20 October 2015 at 21:28, Richard Purdie <
> richard.purdie at linuxfoundation.org> wrote:
>
>> On Mon, 2015-10-19 at 18:52 +0100, Smith, Elliot wrote:
>> > I've done some work on a branch which creates per-build logs for
>> > Toaster, downloadable from the build dashboard:
>> >
>> > poky-contrib, elliot/toaster/wrong_log-8373-v2
>> >
>> > (to fix https://bugzilla.yoctoproject.org/show_bug.cgi?id=8373)
>>
>> Seems reasonably, the only thing I wondered was whether we could somehow
>> capture the build header from the build rather than having to invent a
>> new function for toaster...
>>
>
> I'm not sure we can pick that up as it's written before the BuildStarted
> event, which is the first thing toasterui knows about the build (unless
> there's an earlier event we can capture).
>
> I will investigate whether we can at least reuse the function which
> outputs the header, which I think is in the .bbclass files.
>

In the end, Brian came up with a solution, which was to use the
ParseStarted event rather than the BuildStarted event. This means our log
files are gathering bitbake's output by the time the "Build Configuration"
is output, which means I can remove my code which duplicated that.

I posted a new version to the toaster mailing list for review.

Thanks for your feedback.
Elliot
-- 
Elliot Smith
Software Engineer
Intel Open Source Technology Centre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20151022/0edde247/attachment.html>