Inserting an unresolvable dependency (e.g. kexec-tools on ppc) and using bitbake -k can result in a total failure but exit status of 0 (success)
I think this is fixed now. If something is unbuildable an error messages is printed and the presence of any error messages will cause the exit code to be non-zero. $ MACHINE=qemuppc bitbake task-poky-tools -k Loading cache: 100% |#######################################################################################################################| ETA: 00:00:00 Loaded 943 entries from dependency cache. Parsing recipes: 100% |#####################################################################################################################| Time: 00:00:00 Parsing of 773 .bb files complete (736 cached, 37 parsed). 980 targets, 37 skipped, 0 masked, 0 errors. OE Build Configuration: BB_VERSION = "1.11.0" METADATA_BRANCH = "master" METADATA_REVISION = "982955ec922a0ecc649f7cbfb1e79fc95d0bd833" TARGET_ARCH = "powerpc" TARGET_OS = "linux" MACHINE = "qemuppc" DISTRO = "poky" DISTRO_VERSION = "0.9+snapshot-20110224" TARGET_FPU = "" NOTE: Resolving any missing task queue dependencies NOTE: Runtime target 'kexec-tools' is unbuildable, removing... Missing or unbuildable dependency chain was: ['kexec-tools'] ERROR: Nothing RPROVIDES 'kexec-tools' (but /rphome/poky/meta/recipes-core/tasks/task-poky-tools.bb RDEPENDS on or otherwise requires it) NOTE: Preparing runqueue ERROR: All buildable tasks have been run but the build is incomplete (--continue mode). Errors for the tasks that failed will have been printed above. $ echo $? 1
Verify fixed, thanks.