Bug 8706

Summary: Add oe-selftest test for locked signatures
Product: [QA/Testing] Build Testing Reporter: Paul Eggleton <bluelightning>
Component: generalAssignee: Daniel Istrate <daniel.alexandrux.istrate>
Status: RESOLVED FIXED QA Contact: Costin <costin.c.constantin>
Severity: enhancement    
Priority: Medium+ CC: alexandru.c.georgescu, richard.purdie
Version: unspecified   
Target Milestone: 2.1 M3   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

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)