[bitbake-devel] [PATCH] Lower priority of debug messages that should not be shown on the console

[Adrian Bunk]

On Sun, Feb 23, 2020 at 11:53:57PM +0000, Richard Purdie wrote:
> On Sun, 2020-02-23 at 21:51 +0200, Adrian Bunk wrote:
> > On Sat, Feb 22, 2020 at 03:54:54PM +0000, Richard Purdie wrote:
> > > ...
> > > b) We actually fix/improve the way logging works.
> > > 
> > > I'd prefer b).
> > 
> > Makes sense, I've submitted this as bug #13813.
> 
> I note you believe this has to be fixed before we reach M3. I guess I'd
> agree, I just don't know who is going to do it.

I would have said M4, but that doesn't really change anything.

> Bitbake bugs get auto assigned to me. I physically cannot actually keep
> up with the incoming bugs despite working more than I should.
> 
> I was actually trying to do something about my bug count as its
> seriously depressing me. For each one I try and fix I seem to find
> three more intermittent issues on the autobuilder :(.

I know this might sound brutal, but in hindsight the hash equivalence 
work was not a good idea with the current resourcing.

I fully understand why it is attractive to properly fix a long-standing
problem, but the hash equivalence work and followup fixes might have 
been the difference between an OKish workload and working more than
you should have done.

> I know you didn't mean it this way and we need to track the issues, I
> just don't know how we're going to handle it.

>From my side the problem is that my initial patch is what I can do with 
reasonable effort.

> Cheers,
> 
> Richard

cu
Adrian