| Summary: | In analysis mode, if you interrupt the bitbake build, toaster erroneously reports a successful build | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Toaster | Reporter: | brian avery <brian.avery> |
| Component: | toaster | Assignee: | Elliot Smith <elliot.smith> |
| Status: | RESOLVED FIXED | QA Contact: | Libertad <libertad.gonzalez.de.la.cruz> |
| Severity: | normal | ||
| Priority: | Medium | CC: | belen.barros.pena, jessica.zhang, stanciux.mihail |
| Version: | 2.1 | ||
| Target Milestone: | 2.2 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | Regression (Used to work) |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | 6787 | ||
| Bug Blocks: | |||
|
Description
brian avery
2015-10-14 23:35:36 UTC
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. |