Bug 291 - Bitbake logging is broken
Summary: Bitbake logging is broken
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 0.9
Hardware: x86 Multiple
: Medium normal
Target Milestone: 0.9 M4
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-09-08 04:38 UTC by Joshua Lock - Disabled
Modified: 2010-12-21 06:07 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified: Program Management
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 Joshua Lock - Disabled 2010-09-08 04:38:48 UTC 
Some logs are not printed at the correct level, such as within bitbake/lib/bb/fetch/__init__.py the runfetchcmd()'s call to bb.msg.debug():

    bb.msg.debug(1, bb.msg.domain.Fetcher, "Running %s" % cmd)

Is not printed to the fetch commands log file, whereas calls to bb.msg.note() are correctly logged, such as the one in bitbake/lib/bb/fetch/git.py:

    bb.msg.note(1, bb.msg.domain.Fetcher, "Creating tarball of git repository")
Comment 1 Richard Purdie 2010-09-08 07:26:40 UTC 
Specifically, bitbake-runtask doesn't inherit logging options from the server.
Comment 3 Joshua Lock - Disabled 2010-10-22 00:42:25 UTC 
Verified the fix