| Summary: | Enhance bitbake's parse error handling to indicate where the failure occured | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Darren Hart <dvhart> |
| Component: | bitbake | Assignee: | Paul Eggleton <bluelightning> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bluelightning, poky.bs.watcher, poky.watcher |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | Patch merged (12 Mar) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Darren Hart
2011-11-22 11:37:16 UTC
Darren, I don't suppose you have the actual change that triggered this do you? (In reply to comment #1) > Darren, I don't suppose you have the actual change that triggered this do you? Sorry, I don't. I should have included that. I believe adding any shell-syntax statement into a python function should readily duplicate the result though. I think http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ebc0d4252a19e6ab38052473e54138d29b172dfc will have addressed this problem, it does in other variable expansion error cases. Another case where this happens is here:
$ bitbake linux-yocto -e
ERROR: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure for URL: 'git:///home/dvhart/source/linux/linux-yocto-3.2.git;protocol=file;nocheckout=1;branch=yocto/standard/fri2,meta;name=machine,meta'. The command git ls-remote file:///home/dvhart/source/linux/linux-yocto-3.2.git yocto/standard/fri2 gave empty output unexpectedly
ERROR: Command execution failed: Exited with 1
NOTE: Error expanding variable do_patch
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
I'm trying to setup the fri2 to use linux-yocto-3.2 and am using meta-kernel-dev, which replaces the SRC URI in a non-version specific way. I believe the above is failing because it is still trying to use linux-yocto-3.0, but I can't search for PREFERRED_PROVIDER because it fails before getting there. Printing out which recipe it's working on when it fails would help a lot.
Reopening as this clearly needs more attention. I've sent a trivial fix to bitbake-devel for this issue: http://lists.linuxtogo.org/pipermail/bitbake-devel/2012-March/002111.html This is now fixed in master revision d599d90fd56a7ad12a376011453513d874b512de - an additional NOTE is logged upon error containing the recipe file name. |