Bug 1322

Summary: -k option allows bitbake to return 0 on non-existent target
Product: [Build System, Metadata & Runtime] BitBake Reporter: Paul Eggleton <bluelightning>
Component: bitbakeAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: poky.bs.watcher, poky.watcher, sgw
Version: unspecified   
Target Milestone: 1.1   
Hardware: All   
OS: Multiple   
Whiteboard: Patch on mailing list for review
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Paul Eggleton 2011-08-03 04:49:22 UTC 
If you run bitbake -k doesnotexist the return code is 0:

------- snip -------
ERROR: Nothing PROVIDES 'doesnotexist'
NOTE: Resolving any missing task queue dependencies
NOTE: Tasks Summary: Attempted 0 tasks of which 0 didn't need to be rerun and 0 failed.
paul@helios:~/poky/poky/build$ echo $?
0
------- snip -------

This can be bad for the autobuilder because tasks that actually failed look like they succeeded:

http://autobuilder.yoctoproject.org:8010/builders/crownbay-noemgd/builds/27/steps/shell_10/logs/stdio