| Summary: | reproducibility test does not display actual error log in case of build failure | ||
|---|---|---|---|
| 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, richard.purdie |
| Version: | unspecified | ||
| Target Milestone: | 5.2 M2 | ||
| 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
2024-11-20 23:20:42 UTC
(CC'ing Richard since he reported it) @Richard, any advice on how to handle this? My first thought is to extract lines matching "^ERROR:.*" from logs and display those after the normal logs. Is that a good idea? Yoann to add a message to point the full log. Also dump the error with ~10 lines of context around the error. Fix merged: selftest/reproducible: Print full log path on failure - openembedded-core - OpenEmbedded Core layer https://git.openembedded.org/openembedded-core/commit/?id=1c2287849a2742445d80c81d6a1c6c3e3668765e selftest/reproducible: Print error context on failure - openembedded-core - OpenEmbedded Core layer https://git.openembedded.org/openembedded-core/commit/?id=b3bc820e58b65a976e0abce85fcdffd067697ecf |