| Summary: | Python tasks should output all logging data, similar to shell tasks | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Mark Hatle <mark.hatle> |
| Component: | meta-yocto | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, ke.yu, kevin.tian, poky.bs.watcher, poky.watcher, richard.purdie, sgw |
| Version: | 0.9 | ||
| Target Milestone: | 1.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | Patch our for review | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Mark Hatle
2010-09-09 08:56:41 UTC
See bug 377. This is the opposite issue to that problem. We need to ensure that all of the messages generated by a task: note, warning, error, debug... get logged to the task logs, similar to what happens already via shell scripts that run. Specifically, the debug messages for the task should go to the logfile even if they don't go to the console. Richard, it is already fixed, right? Specifically at the bitbake level we need to separate the level handling for the different handlers. The handler setup in bin/bitbake should be controlled by the current level handling but the handler in build.py should have the option of using a different log level. The core logger should have its level left unset. This is an invasive change for 1.0 at this point so I'd prefer to leave it for 1.1. The underlying problem of log data not making it to the log files has been fixed. http://lists.linuxtogo.org/pipermail/bitbake-devel/2011-July/001034.html is a start at what we'd need to resolve this bug The final pieces of this merged in http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=7ee93b206a6389e6eb7b9440dc2fae801c77bc9b |