[bitbake-devel] bitbake/logging: Overhaul internal logging process

[Richard Purdie]

On Fri, 2011-08-12 at 08:36 -0700, Chris Larson wrote:
> On Fri, Aug 12, 2011 at 8:31 AM, Tom Rini <tom.rini at gmail.com> wrote:
> > On Fri, Aug 12, 2011 at 7:25 AM, Richard Purdie
> > <richard.purdie at linuxfoundation.org> wrote:
> >> At the moment it bugs me a lot that we only have one effective logging
> >> level for bitbake, despite the logging module having provision to do
> >> more advanced things. This patch:
> >>
> >> * Changes the core log level to the lowest level we have messages of
> >>  (DEBUG-2) so messages always flow through the core logger
> >> * Allows build.py's task logging code to log all the output regardless
> >>  of what output is on the console and sets this so log files now
> >>  always contain debug level messages even if these don't appear
> >>  on the console
> >> * Moves the verbose/debug/debug-domains code to be a UI side setting
> >> * Adds a filter to the UI to only print the user requested output.
> >
> > Can we also get a way (or big enough log level) to get timestamps thrown in?
> 
> I think it would be nice to provide a way to influence the format
> string used by the formatter in the UI, either directly, or via a
> logging configuration file as supported by the logging module.

Agreed, but that one is for a different patch.

Cheers,

Richard