Bug 9595 - Extensible sdk: error early if tasks to be ran cannot be provided from sstate
Summary: Extensible sdk: error early if tasks to be ran cannot be provided from sstate
Status: RESOLVED OBSOLETE
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.1
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.2
Assignee: Randy Witt
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-05-05 16:29 UTC by Randy Witt
Modified: 2016-10-25 19:57 UTC (History)
3 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 Randy Witt 2016-05-05 16:29:22 UTC 
Right now when running the extensible sdk, if an item is not found in locked signatures it will run the task and build it. This behavior is fine for items that have been specifically unlocked.

Currently there is an error/warning you can turn on for a task not being in sstate. However, this runs for all tasks in the task graph, not just the ones that will actually run. So ideally we would expand that to instead only error if the tasks to be ran don't exist in sstate.
Comment 1 Paul Eggleton 2016-05-05 18:43:09 UTC 
At least part of this may be covered under bug 9367.
Comment 2 Randy Witt 2016-10-25 19:57:09 UTC 
This bug is obsolete since BB_SETSCENE_ENFORCE in conjunction with locked signatures should address the issue.