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

[Richard Purdie]

On Fri, 2020-02-21 at 22:52 +0200, Adrian Bunk wrote:
> Signed-off-by: Adrian Bunk <bunk at stusta.de>
> ---
>  bitbake/lib/bb/runqueue.py | 8 ++++----
>  bitbake/lib/bb/siggen.py   | 6 +++---
>  2 files changed, 7 insertions(+), 7 deletions(-)

The trouble here is that if we remove these messages (and I can
understand why people want to), if there is a problem with hashequiv, I
can simply look at the result and say "yes, it broke" with zero ability
to understand why as we can't tell what happened in the build.

The correct fix is probably to change the console log messages to log
differently to the on disk log file. Even then, it means we can't debug
autobuilder failures unless we save those logs.

So in summary, there is a choice:

a) We can compel me to merge patches like this. I will then just have
to close all hashequiv bug reports as WORKSFORME.

b) We actually fix/improve the way logging works.

I'd prefer b).

Cheers,

Richard