| Summary: | reproducible: in case of an error, the saved log does not contain detailed task log | ||
|---|---|---|---|
| Product: | [QA/Testing] Functional (self) Testing | Reporter: | Yoann Congal <yoann.congal> |
| Component: | oe-selftest | Assignee: | Yoann Congal <yoann.congal> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 5.3 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Yoann Congal
2025-03-16 00:12:36 UTC
Suspicious code is in https://git.yoctoproject.org/poky/tree/bitbake/lib/bb/ui/knotty.py#n354: def print_event_log(event, includelogs, loglines, termfilter): ... bb.error("Logfile of failure stored in: %s" % logfile) if includelogs and not event.errprinted: print("Log data follows:") ... for line in lines: print(line) => print_event_log prints on stdout bypassing the log framework. Refactor this to use the log framework instead? Note: the commit introducing this function is: --- commit 24879df071d4803db3d39ae1d5cad852daa92f28 Author : Paul Eggleton <paul.eggleton@linux.intel.com> Thu Aug 31 01:30:44 2017 tinfoil: ensure log lines get printed when tasks fail If a task fails during build_targets(), we need to print out the log lines as knotty does or the user will be missing information about the failure. (This should get some deeper refactoring, but now isn't the time for that.) --- Maybe now is the time for that? ;) Patch sent: [PATCH] knotty: pass failed task logs through the log infrastructure https://lists.openembedded.org/g/bitbake-devel/message/17611 |