| Summary: | Add 'paths searched to sstate object' to the data collected about tasks | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Toaster | Reporter: | Belen Barros Pena <belen.barros.pena> | ||||
| Component: | toaster | Assignee: | Alexandru Damian <alexandru.damian> | ||||
| Status: | VERIFIED OBSOLETE | QA Contact: | Mihail Stanciu <stanciux.mihail> | ||||
| Severity: | enhancement | ||||||
| Priority: | Medium | CC: | alexandru.damian, belen.barros.pena, stanciux.mihail | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 1.6 | ||||||
| Hardware: | All | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
I'm not sure if this can't be done at UI level by displaying the SSTATE_DIR and SSTATE_MIRRORS. Do we need different information here ? (In reply to comment #1) > I'm not sure if this can't be done at UI level by displaying the SSTATE_DIR > and SSTATE_MIRRORS. Do we need different information here ? I am not sure the above would be enough. There are 2 pieces of information we'd like to show: 1. If the sstate object was found, where? 2. If the sstate object was searched in places other than 1, where? So a successful sstate task will have 1, but it might or might not have 2. An example here: http://www.yoctoproject.org/toaster/task-details-prebuilt-sstate.html A failed sstate task will not have 1, but will have 2. Examples here: http://www.yoctoproject.org/toaster/task-details-sstate-missed.html http://www.yoctoproject.org/toaster/task-details-sstate-failed.html The key thing is identifying where within the places listed in SSTATE_DIR and SSTATE_MIRRORS the object was found, and which places where searched unsuccessfully. If the shared state object is found, we show the uri where it was found. If the shared state object is not found, we show the uri(s) where it was searched (SSTATE_DIR and SSTATE_MIRRORS) Verified. |
Created attachment 1535 [details] Task information to be collected When creating the list of information to be collected about tasks, we decided to include the following: * The path where the sstate object was found (path_to_sstate_obj) * The path to the Python / Shell script executed for a task (source_url) * Path(s) searched to sstate object: BitBake's shared state code works by looking in SSTATE_DIR and SSTATE_MIRRORS for shared state files. This piece of information shows the path(s) BitBake searched for files for a certain task. The path searched should only display when different from path_to_sstate_obj The latter is missing from the Tasks Django model, and it should be added, being particularly useful for tasks with sstate_result returning 'missing' or 'failed'.