Bug 14085 - Toaster UI should know when bitbake crashed
Summary: Toaster UI should know when bitbake crashed
Status: RESOLVED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 3.3
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 4.0 M4
Assignee: David Reyna
QA Contact: Toaster default assignee
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2020-10-13 15:03 UTC by Tim Orling
Modified: 2022-03-22 02:31 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
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 Tim Orling 2020-10-13 15:03:42 UTC 
While working on Bug 14079, it is frustrating that the toaster UI hangs on "Tasks starting..." even though bitbake has already crashed and dumped to toaster_ui.log

The front end should be smart enough to immediately halt and catch fire. It should not just hang and give the user a false sense of hope. "She's dead Jim"
Comment 1 David Reyna 2020-10-13 16:51:07 UTC 
I did add code a while back to capture and report when clones fail and other various code crashes, but this one slipped that net.

I will fix it.
Comment 2 Tim Orling 2022-03-14 17:27:40 UTC 
In particular, we need to capture when there is a Traceback in toaster_ui.log
Comment 3 David Reyna 2022-03-21 21:15:38 UTC 
Patch sent to bitbake list.
Comment 4 David Reyna 2022-03-22 02:31:57 UTC 
Pushed

Commit: 4769eaebb40772fca1af6d59b104cc0db00fbbc5