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
http://lists.openembedded.org/pipermail/bitbake-devel/2020-March/020973.html
(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.
http://lists.openembedded.org/pipermail/bitbake-devel/2020-March/020979.html