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

[Richard Purdie]

On Mon, 2020-02-24 at 07:49 +0200, Adrian Bunk wrote:
> 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.

Technically its feature work although I guess it can be argued both
ways as its also a usability/bug fix.

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

Not brutal, in hindsight it hasn't been such a good idea.

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

Agreed, and now why I kind of feel guilty if I don't resolve some of
the issues. We could just turn it off again I guess, I keep wondering
about that.

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

Part of the reason I'm highlighting this is that I have a lot of
feedback that says people don't believe there is any problem with our
resourcing. Unless I can show where there are issues, its not going to
change :/.

Cheers,

Richard