Bug 13813 - bitbake hashequiv messages in the console are too verbose
Summary: bitbake hashequiv messages in the console are too verbose
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 3.1
Hardware: All Multiple
: High normal
Target Milestone: 3.1 M4
Assignee: Joshua Watt
QA Contact:
URL:
Whiteboard: with backport
Depends on:
Blocks:
 
Reported: 2020-02-23 19:48 UTC by Adrian Bunk
Modified: 2020-03-16 13:40 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Bunk 2020-02-23 19:48:49 UTC
Hashequiv messages in the console are too verbose.
For the past months on master this was OK, but this is debug info that should not by default spam the console of the user in a stable release.
These messages should be logged to a file, which should be made available from the autobuilder.

For background see
http://lists.openembedded.org/pipermail/bitbake-devel/2020-February/020914.html
http://lists.openembedded.org/pipermail/bitbake-devel/2020-February/020917.html
Comment 2 Adrian Bunk 2020-03-11 09:57:19 UTC
(In reply to comment #1)
> http://lists.openembedded.org/pipermail/bitbake-devel/2020-March/020973.html

Thanks a lot for working on this.

One message is left for me with these patches in poky master-next:

Sstate summary: Wanted 802 Found 0 Missed 802 Current 557 (0% match, 40% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
NOTE: Setscene tasks completed
NOTE: Setscene tasks completed
NOTE: Setscene tasks completed
NOTE: Setscene tasks completed
NOTE: Setscene tasks completed
NOTE: Setscene tasks completed
...
NOTE: Setscene tasks completed
NOTE: Tasks Summary: Attempted 3630 tasks of which 2475 didn't need to be rerun and all succeeded.


This "Setscene tasks completed" is displayed ~ 100 times during this build of an image after pulling in the latest changes from master-next.

Unless it is a bug that this "completed" happened more then once, it should also not be displayed by default.