| Summary: | Bitbake logging is broken | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Joshua Lock - Disabled <josh> |
| Component: | meta-yocto | Assignee: | Richard Purdie <richard.purdie> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, kevin.tian, poky.bs.watcher, poky.watcher, richard.purdie, sgw |
| Version: | 0.9 | ||
| Target Milestone: | 0.9 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Program Management | Documentation change: | --- |
Specifically, bitbake-runtask doesn't inherit logging options from the server. Verified the fix |
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")