8706 2015-11-19 19:19:05 +0000 Add oe-selftest test for locked signatures 2016-03-31 15:13:36 +0000 1 1 10 QA/Testing Build Testing general unspecified All Multiple RESOLVED FIXED Medium+ enhancement 2.1 M3 1 bluelightning daniel.alexandrux.istrate alexandru.c.georgescu richard.purdie costin.c.constantin --- --- No (bug/feature does not impact docs) oldest_to_newest 56666 0 bluelightning 2015-11-19 19:19:05 +0000 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) 59005 1 daniel.alexandrux.istrate 2016-02-15 13:47:11 +0000 Patch sent to ML: http://lists.openembedded.org/pipermail/openembedded-core/2016-February/117548.html 60605 2 richard.purdie 2016-03-31 15:13:36 +0000 http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=4a2182741598eff4d8c0acee30bbf335f11615bd