[bitbake-devel] [PATCH] cooker: Ensure BB_CONSOLE remains correct over server resets

[Smith, Elliot]

On 16 October 2015 at 16:59, Richard Purdie <
richard.purdie at linuxfoundation.org> wrote:

> On Fri, 2015-10-16 at 16:57 +0100, Smith, Elliot wrote:
> > On 11 October 2015 at 10:22, Richard Purdie
> > <richard.purdie at linuxfoundation.org> wrote:
> >         The console log data is written to is created at console
> >         initialisation
> >         time and does not change over reset events. This ensures the
> >         BB_CONSOLELOG value is correct over such resets by preserving
> >         it.
> >
> > I've put your three patches on top of master and ran a few builds. The
> > result is that all of the logs for those builds are going into a
> > single timestamped file. Before, they went to separate files. Is this
> > intentional, or was the old behaviour incorrect? (Ideally, toaster
> > needs a separate log file for each build.)
> >
> It should generate one log file for each "session". A session would be
> one logfile for all bitbake memory resident transactions and a log file
> for each commandline transaction.
>
> It is a "console log", not an individual build log.
>

Thanks for clarifying.

Will these patches be in 2.0? From the toaster point of view, it would be
better if the current behaviour remained for now, even though it is broken.

We are working on a solution which will write separate build logs from
within Toaster itself, which will mean we can keep our log download working
when your patches do go in.

However, we may not get this finished for 2.0, and it would be good if we
could keep the Toaster log download feature working in the meantime.

Thanks.
Elliot

-- 
Elliot Smith
Software Engineer
Intel Open Source Technology Centre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/bitbake-devel/attachments/20151019/4c5178a2/attachment-0002.html>