To replicate: 1)run toaster in analysis mode 2) do bitbake bash 3) allow it to get into the tasks running (like a do_configure or 2) 4)Ctrl-c the bitbake. Toaster shows a green build. Bitbake cli says: Keyboard Interrupt, closing down... NOTE: Tasks Summary: Attempted 202 tasks of which 0 didn't need to be rerun and all succeeded. ERROR: Command execution failed: Stopped build Summary: There was 1 WARNING message shown. Summary: There was 1 ERROR message shown, returning a non-zero exit code. Execution was interrupted, returning a non-zero exit code.
Builds interrupted on the command line count as cancelled and need the same design (i.e. https://bugzilla.yoctoproject.org/attachment.cgi?id=2706), hence the dependency on bug 6787.
I just tried this. The builds started from cli that you cancel no longer show as failed: they just stay forever as running, until you stop Toaster. When you restart Toaster, they show as failed.
Submitted for review: https://lists.yoctoproject.org/pipermail/toaster/2016-April/004511.html
The old BuildCompleted event with an _interrupted flag no longer appears to be fired, which is what I was previously using to notice when the bitbake build was interrupted. Needs further work to figure out if there's now an event for interrupted builds which we could cancel (might need to change the event mask to be able to see this).
Sent v2 for review: https://lists.yoctoproject.org/pipermail/toaster/2016-April/004521.html
Now in bitbake master.