| Summary: | Distinguish between executed, existing, sstate and covered tasks | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Toaster | Reporter: | Belen Barros Pena <belen.barros.pena> |
| Component: | toaster | Assignee: | Alexandru Damian <alexandru.damian> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | jessica.zhang |
| Version: | unspecified | ||
| Target Milestone: | 1.5 M1 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | |||
| Bug Blocks: | 4650 | ||
|
Description
Belen Barros Pena
2013-04-12 11:19:13 UTC
Question about this classification: isn't a missed task a built task? Basically, for a given task the checksum changed, so it was rebuilt. If we apply this classification, wouldn't we end up with 2 entries for the same task in the tasks table (one missed, one rebuilt)? We should clear this up with RP, Ross and Paul E, who came up with the task classification. We have decided to classify tasks into 2 main types: 1. Executed: tasks that build something 2. Prebuilt: tasks that don't built anything The above tasks types can have the following outcomes: 1. Executed tasks: 1.1 Succeeded: executed tasks that complete 1.2 Failed: executed tasks that don't complete 2. Prebuilt tasks: 2.1 Existing: prebuilt tasks for which BitBake finds a stamp file 2.2 Sstate: prebuilt tasks that complete reusing sstate objects 2.3 Covered: prebuilt tasks brought in by sstate tasks For more details see the Django db tasks model at: https://wiki.yoctoproject.org/wiki/Django_models And bug 4275 Merged in origin/master and origin/dora-toaster. Verified fixed in: master: 76751a03b1475f22499c488395274453096b9c38 dora-toaster: 4b64eb444ab065915267d8040bf878ecae9b00c4 |