| Summary: | Toaster needs to expose errors/warnings in its own logs | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Toaster | Reporter: | Paul Eggleton <bluelightning> | ||||||
| Component: | toaster | Assignee: | Tim Orling <tim.orling> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Medium | CC: | alexandru.damian, belen.barros.pena, cristiana.voicu, david.reyna, jessica.zhang, jose.perez.carranza, tim.orling | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 4.0 | ||||||||
| Hardware: | Cheifriver | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | GUI design available | ||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||||
| Attachments: |
|
||||||||
|
Description
Paul Eggleton
2014-04-16 13:32:14 UTC
Created attachment 2243 [details]
Design - Expose Toaster errors in the UI
Created attachment 2547 [details]
Design - Expose Toaster errors in the UI
Changes slightly the position of the Toaster errors link to accommodate other actions in the same area
Given the pain of debugging toasterui failures during 3.2 cycle, we really need to improve the logging/log handling. This has been fixed in two steps. 1) All errors in up to the launch of the build, including all steps of cloning, have been captured and reported. 2) All errors after the launch of the build that are not normally caught and reported by bitbake, specifically crashes in bitbake itself, are now captured and reported (see 14085). |