Bug 5776 - Identify tasks with SSTATE_RESULT = 1 (SSTATE_MISS)
Summary: Identify tasks with SSTATE_RESULT = 1 (SSTATE_MISS)
Status: VERIFIED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.6 M4
Assignee: Alexandru Damian
QA Contact: Mihail Stanciu
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-01-30 14:27 UTC by Belen Barros Pena
Modified: 2014-07-25 11:14 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

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 Belen Barros Pena 2014-01-30 14:27:52 UTC 
In order to implement the Cache attempt filter in the tasks table and the task detail pages we need a way to identify the tasks that attempt to reuse an sstate object but can't because the required sstate object is not found (i.e. tasks with SSTATE_RESULT = 1 in our model).
Comment 1 Belen Barros Pena 2014-02-13 12:19:14 UTC 
Alex will try to get BitBake to tell us about this. If it doesn't work or it impacts performance, we can fall back to the hardcoding solution.

We also agreed that for failed _setscene tasks we will set the SSTATE_RESSULT to 2 (SSTATE_FAILED) in the real task
Comment 2 Alexandru Damian 2014-02-21 14:32:51 UTC 
Patches on the mailing list.
Comment 4 Mihail Stanciu 2014-07-25 11:14:51 UTC 
Verified.