Re: [PATCH] cooker: Ensure BB_CONSOLE remains correct over server resets

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Mon, 2015-10-19 at 10:32 +0000, Barros Pena, Belen wrote:
> 
> On 16/10/2015 16:59, "bitbake-devel-bounces@lists.openembedded.org on
> behalf of Richard Purdie" <bitbake-devel-bounces@lists.openembedded.org on
> behalf of richard.purdie@linuxfoundation.org> wrote:
> 
> >On Fri, 2015-10-16 at 16:57 +0100, Smith, Elliot wrote:
> >> Thanks for these, Richard.
> >>
> >> On 11 October 2015 at 10:22, Richard Purdie
> >> <richard.purdie@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.

When you say "ran a few builds", was this with toaster? I'd like to
double check we are seeing the right behaviour but it depends how you
actually ran the builds as to whether this was the right result.

>  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.
> 
> Mmmm, for Toaster we need an individual build log, not a console log :/

Since toaster records all the log information, is it not able to compute
an individual build log from that data?

The reason I'm reluctant to just add some kind of "build log"
functionality to bitbake is that at the commandline level, I think it
would mislead people. In theory, a "build" would be the output between
BuildStarted and BuildCompleted, the question is then what happens to
the output before and after these events.

Cheers,

Richard