12693 2018-04-17 17:12:32 +0000 Task added after do_deploy not cached 2018-04-19 14:35:01 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 2.4 x86 arm64 RESOLVED NOTABUG Medium normal 4.99 1 jon.richardson ross.burton meta.mr.watcher meta.watcher scott.branden stephano --- --- Don't know oldest_to_newest 80279 0 jon.richardson 2018-04-17 17:12:32 +0000 In my u-boot recipe I have the following: require recipes-bsp/u-boot/u-boot.inc python () { if (d.getVar('SOMEVAR', True) == 'true': bb.build.addtask('do_signing', 'do_build', 'do_deploy', d) } do_signing() { # Do something with ${DEPLOY_DIR_IMAGE}/${UBOOT_BINARY} } If I build the recipe do_signing gets run after do_deploy properly. If I do a bitbake myrecipe -c cleanall, then bitbake brcm-myrecipe, do_signing is run even though the setscene version of all the tasks is run. If do_deploy_setscene is run shouldn't do_signing which depends on it be ignored since it's cached? do_package_write_rpm_setscene (191480): log.do_package_write_rpm_setscene.191480 do_package_qa_setscene (192008): log.do_package_qa_setscene.192008 do_populate_sysroot_setscene (193016): log.do_populate_sysroot_setscene.193016 do_populate_lic_setscene (193164): log.do_populate_lic_setscene.193164 do_deploy_setscene (193310): log.do_deploy_setscene.193310 do_packagedata_setscene (195065): log.do_packagedata_setscene.195065 do_signing (69150): log.do_signing.69150 80346 1 ross.burton 2018-04-19 14:35:01 +0000 sstate is opt-in, if your task doesn't put anything into the cache then it can't be restored either. If you want your recipe to use sstate then look up sstate-inputdirs and sstate-outputdirs in the manual and other classes in oe-core.