Bug 6170 - Toaster needs to expose errors/warnings in its own logs
Summary: Toaster needs to expose errors/warnings in its own logs
Status: RESOLVED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: Cheifriver Multiple
: Medium normal
Target Milestone: 4.0
Assignee: Tim Orling
QA Contact:
URL:
Whiteboard: GUI design available
Depends on:
Blocks:
 
Reported: 2014-04-16 13:32 UTC by Paul Eggleton
Modified: 2022-03-21 21:19 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Design - Expose Toaster errors in the UI (314.87 KB, application/pdf)
2014-11-13 17:35 UTC, Belen Barros Pena 		no flags Details
Design - Expose Toaster errors in the UI (318.42 KB, application/pdf)
2015-06-12 14:09 UTC, Belen Barros Pena 		no flags Details
Show Obsolete (1) Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2014-04-16 13:32:14 UTC 
The Toaster BitBake UI logs its own errors to toaster_ui.log. If the user does not look in this file they will not notice when errors occur; if we're lucky they might notice missing data, but it's likely that in some cases they won't know what they are looking at. Toaster needs to record these errors and display them in the web part of the UI.
Comment 1 Belen Barros Pena 2014-11-13 17:35:09 UTC 
Created attachment 2243 [details]
Design - Expose Toaster errors in the UI
Comment 2 Belen Barros Pena 2015-06-12 14:09:12 UTC 
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
Comment 3 Tim Orling 2020-11-05 08:08:02 UTC 
Given the pain of debugging toasterui failures during 3.2 cycle, we really need to improve the logging/log handling.
Comment 4 David Reyna 2022-03-21 21:19:40 UTC 
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).