[OE-core] [PATCH 0/3] recipetool/devtool: send errors to stderr
Paul Eggleton
paul.eggleton at intel.com
Sat Dec 12 07:00:05 UTC 2015
On Fri, 11 Dec 2015 17:09:33 Christopher Larson wrote:
> On Wed, Sep 23, 2015 at 11:21 AM Christopher Larson <kergoth at gmail.com>
>
> wrote:
> > From: Christopher Larson <chris_larson at mentor.com>
> >
> > This aligns with the behavior of bitbake proper. There is a bit of code
> > duplication between knotty and scriptutils, but that's not new -- that was
> > the
> > case before as well. We should consider moving these logger configuration
> > functions into bb.msg.
> >
> > The following changes since commit
> >
> > 2ad7308ee7166641eff99f3b9fe6794de143f6bc:
> > oeqa/utils/qemurunner.py: Remove duplicate message on LoggingThread
> >
> > start (2015-09-22 18:13:02 +0100)
> >
> > are available in the git repository at:
> > git://github.com/kergoth/openembedded-core scriptutils-log-improvements
> >
> > https://github.com/kergoth/openembedded-core/tree/scriptutils-log-improvem
> > ents>
> > Christopher Larson (3):
> > oe.scriptutils: enable color in a more flexible way
> > oe.scriptutils: add logger_setup_filters
> > recipetool, devtool: set up the logging filters
>
> Does anyone happen to know if there any objection to this? I just noticed
> this hasn't been merged yet. This makes the behavior of recipetool and
> devtool more consistent with bitbake itself by sending errors to stderr.
> Long term I'd like to see warnings go there as well, but that could be more
> controversial and is a later task, I think this should go in as is.
> Eventually we should consolidate some of the logger setup and configuration
> logic between scriptutils and bitbake as well, but that was the case with
> or without this series
I certainly don't - I did see this hadn't been merged a few weeks back, I
should have acked it.
Acked-by: Paul Eggleton <paul.eggleton at linux.intel.com>
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
More information about the Openembedded-core
mailing list