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

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

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. 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.

Cheers,

Richard