Bug 8706 - Add oe-selftest test for locked signatures
Summary: Add oe-selftest test for locked signatures
Status: RESOLVED FIXED
Alias: None
Product: Build Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: unspecified
Hardware: All Multiple
: Medium+ enhancement
Target Milestone: 2.1 M3
Assignee: Daniel Istrate
QA Contact: Costin
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-11-19 19:19 UTC by Paul Eggleton
Modified: 2016-03-31 15:13 UTC (History)
2 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 Paul Eggleton 2015-11-19 19:19:05 UTC 
We need to test that the locked signatures code is working. This would be a matter of:

1) Run bitbake -S none to generate the locked sigs include file

2) "require" this in the configuration and set SIGGEN_LOCKEDSIGS_CHECK_LEVEL = "warn"

3) Build a locked recipe

4) Make a change that should cause the locked task signature to change

5) Run a build, verify you get the warning and that the real task *isn't* run (i.e. the locked signature has worked)