[bitbake-devel] [PATCH] bitbake/runqueue: don't shout about hash updates

Mark Hatle mark.hatle at kernel.crashing.org
Wed Oct 23 15:37:41 UTC 2019


This was from a patch the other day:

-                bb.warn("Deferring %s after %s" % (tid, sqdata.hashes[h]))
+                bb.note("Deferring %s after %s" % (tid, sqdata.hashes[h]))

Is that also debug, or is it really something to be displayed?  (Same file.)

--Mark

On 10/23/19 10:33 AM, Ross Burton wrote:
> With hash equivalency enabled the runqueue logs at level info quite heavily,
> which spams the console.
> 
> Reduce the log level down to debug so it's there if needed but doesn't get in
> the way.
> 
> Signed-off-by: Ross Burton <ross.burton at intel.com>
> ---
>  bitbake/lib/bb/runqueue.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py
> index 18049436fd5..e1eaf49b8cd 100644
> --- a/bitbake/lib/bb/runqueue.py
> +++ b/bitbake/lib/bb/runqueue.py
> @@ -2361,7 +2361,7 @@ class RunQueueExecute:
>              if tid in self.build_stamps:
>                  del self.build_stamps[tid]
>  
> -            logger.info("Setscene task %s now valid and being rerun" % tid)
> +            logger.debug(2, "Setscene task %s now valid and being rerun" % tid)
>              self.sqdone = False
>              update_scenequeue_data([tid], self.sqdata, self.rqdata, self.rq, self.cooker, self.stampcache, self)
>  
> 


More information about the bitbake-devel mailing list