linux/poky.git/bitbake/lib/bb/cooker.py, branch 1.3

bitbake: cooker: adjust layer dependency error messages

2012-09-27T15:45:27+00:00

Make these a little easier to understand. (Bitbake rev: 84ab874c8818484d37ee438aab27486fff497705) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: cooker: Clarify package/recipe wording

2012-09-20T10:56:32+00:00

When the '-s' option is run, change the heading above the list of recipes to say "Recipe Name" instead of "Package Name". (Bitbake rev: d1c3a9de875fb488a56ab5cb1d2f8e2f24f31d69) Signed-off-by: Trevor Woerner Signed-off-by: Richard Purdie

bitbake: cooker: Fix priority for virtual recipes

2012-09-14T08:50:36+00:00

When making filename comparisons for recipes for priority calculations, we need to split off any virtual prefix. Without this, BBCLASSEXTEND version of recipes don't follow the priority settings they should. [YOCTO #2933] (Bitbake rev: 055b72a230e6b0b1cababd65372c62d9ddce385e) Signed-off-by: Richard Purdie

bitbake: cooker: fix handling of exceptions during exception handling

2012-09-10T12:14:08+00:00

If an exception occurs during handling another exception we were getting a useless traceback such as the following, after which BitBake froze: ERROR: Command execution failed: Traceback (most recent call last): File "/home/user/poky/poky/bitbake/lib/bb/command.py", line 84, in runAsyncCommand self.cooker.updateCache() File "/home/user/poky/poky/bitbake/lib/bb/cooker.py", line 1207, in updateCache if not self.parser.parse_next(): File "/home/user/poky/poky/bitbake/lib/bb/cooker.py", line 1694, in parse_next logger.error('Unable to parse %s', value.recipe, AttributeError: 'exceptions.TypeError' object has no attribute 'recipe' Fix this to print an actual traceback of the exception and exit gracefully (well, as gracefully as possible under the circumstances). The general fix for [YOCTO #2977]. (Bitbake rev: 675b237a284dff84e972546774b69e2f89afb360) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: cooker: Add explict handling of BBHandledException for parsing failures

2012-08-23T08:22:43+00:00

This removes some unnecessary tracebacks (Bitbake rev: db0ff7b4d47fce8322dd2350a2b1a6f60ef61d25) Signed-off-by: Richard Purdie

bitbake: cooker: Ensure parsing failures stop the build

2012-08-23T08:22:43+00:00

Currently parsing failures still allow bitbake to continue on and try and execute a build. This is clearly a bad idea and this patch adds in more correct error handling and stops the build. The use of sys.exit is nasty but this patches other usage in this function so is at least consisent and its better than the current situation of trying to execure a half parsed set of recipes. There are probably better ways this could be improved to use to stop the build. (Bitbake rev: 22756e9c0f1da33ba2c6e881b214577a610b7986) Signed-off-by: Richard Purdie

bitbake: cooker: fix traceback when using -b with skipped recipe

2012-08-23T08:22:42+00:00

If a recipe is skipped during parsing for whatever reason, check and report this as an error rather than trying to use the data that is sent back and failing. Fixes [YOCTO #2976]. (Bitbake rev: a324df40243fa55ccc89fd5970d46f25330d0a0d) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: bitbake/cooker: minor refactor of parseConfiguration()

2012-08-22T12:59:56+00:00

All calls to parseConfiguration set self.status and call self.handleCollections() afterwards, so just do this inside parseConfiguration() itself. (Bitbake rev: 3c2322d8a6ce15e20adb07a61aa321d884a9bcca) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: cooker: fix OVERRIDES in BB_SIGNATURE_HANDLER (to override value from DISTRO.conf from local.conf)

2012-08-02T22:04:27+00:00

We really need to pass the finalised data store into the parser init function (and hence the siggen init function). This ensures any value changes get passed into the correct code. (Bitbake rev: 19efc6081c15a59bb8f5aaf8478650a2732cafe8) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

bitbake: cooker.py: Ensure we track parser errors and only show bbappend issues on complete parse

2012-07-24T09:35:33+00:00

Currently if any parsing failure occurs, there can be a long list of bbappends that are "dangling" based on the fact that recipes were not parsed. This change firstly ensures the error counter is incremented and secondly that the bbappends list is only shown on a completed parse list. (Bitbake rev: 358952f0d874b869d361bbd72a5ea317bf939cd3) Signed-off-by: Richard Purdie