Bug 377 - When building there are too many messages
Summary: When building there are too many messages
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 0.9
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 1.0 M1
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-09-30 13:54 UTC by Mark Hatle
Modified: 2011-02-01 09:52 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Hatle 2010-09-30 13:54:33 UTC 
When running a build, there are simply too many messages to accurately understand what is happening in the system.

My suggestion is to have a "quiet" mode for bitbake that simply returns the "Running task" messages, and any warnings, errors or fatal messages.

it looks on first glance as if Bitbake may have the ability to do some of this already via the note function by setting a specific logging level.
Comment 1 Mark Hatle 2010-10-11 07:00:05 UTC 
See bug 304 for the opposite effect.

Console logging messages need to be reduced by default, to allow us to more easily understand what is happening..  While "internal" (file) logging is likely good today, or may even be slightly expanded.
Comment 2 Richard Purdie 2011-02-01 09:52:34 UTC 
This has been fixed with the logging changes in master.