From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Tell me your build error message annoyances!
Date: Thu, 09 Jun 2011 12:02:10 +0100 [thread overview]
Message-ID: <1307617330.2529.4803.camel@phil-desktop> (raw)
In-Reply-To: <4DE56B0D.4020209@intel.com>
On Tue, 2011-05-31 at 15:26 -0700, Scott Garman wrote:
> I'd like to collect some feedback on error messages while building that
> you find confusing/annoying/unhelpful. I'm going to be working on trying
> to improve the situation and would like to hear from you about what
> could be more helpful.
Here's another one which, although perhaps slightly off-topic for your
current effort, still seems to fall into all three of the categories you
mentioned :-)
After I made a typo (mismatched quotes) in one of my recipes, my next
bitbake run printed:
Loading cache: 100% |#####################################################################################################################################################| ETA: 00:00:00
Loaded 1323 entries from dependency cache.
NOTE: Error expanding variable do_configure | ETA: --:--:--
ERROR: Command execution failed: Traceback (most recent call last):############################# | ETA: 00:00:00
File "/home/pb/oe/bitbake/lib/bb/command.py", line 99, in runAsyncCommand
self.cooker.updateCache()
File "/home/pb/oe/bitbake/lib/bb/cooker.py", line 871, in updateCache
if not self.parser.parse_next():
File "/home/pb/oe/bitbake/lib/bb/cooker.py", line 1120, in parse_next
self.shutdown(clean=False)
File "/home/pb/oe/bitbake/lib/bb/cooker.py", line 1102, in shutdown
bb.codeparser.parser_cache_save(self.cfgdata)
File "/home/pb/oe/bitbake/lib/bb/codeparser.py", line 77, in parser_cache_save
data, version = p.load()
EOFError
So, this is (a) confusing, because "EOFError" doesn't yield much
information about the actual cause of the problem; (b) unhelpful, since
it doesn't mention which line of the file (or even which recipe) was to
blame; and (c) annoying, for the usual reasons to do with python
traceback.
Somewhat worse, even after I fixed the typo, any subsequent attempt to
run bitbake would just result in:
Loading cache: 100% |#####################################################################################################################################################| ETA: 00:00:00
Loaded 1323 entries from dependency cache.
Traceback (most recent call last): | ETA: --:--:--
File "/usr/lib/python2.6/multiprocessing/util.py", line 235, in _run_finalizers
finalizer()
File "/usr/lib/python2.6/multiprocessing/util.py", line 174, in __call__
res = self._callback(*self._args, **self._kwargs)
File "/home/pb/oe/bitbake/lib/bb/codeparser.py", line 77, in parser_cache_save
data, version = p.load()
EOFError
(repeated about 10 times)
I deleted tmp/cache/* and that seemed to fix the problem.
p.
next prev parent reply other threads:[~2011-06-09 11:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 22:26 Tell me your build error message annoyances! Scott Garman
2011-06-01 1:34 ` mark gross
2011-06-01 15:06 ` Phil Blundell
2011-06-01 16:25 ` Richard Purdie
2011-06-01 16:58 ` Chris Larson
2011-06-03 14:35 ` mark gross
2011-06-03 14:48 ` Paul Eggleton
2011-06-02 14:17 ` Phil Blundell
2011-06-02 7:34 ` Martin Jansa
2011-06-03 6:10 ` Darren Hart
2011-06-03 8:11 ` Richard Purdie
2011-06-03 14:22 ` Mark Hatle
2011-06-03 15:43 ` Phil Blundell
2011-06-03 15:47 ` Chris Larson
2011-06-07 4:53 ` Darren Hart
2011-06-07 9:18 ` Richard Purdie
2011-06-06 21:13 ` Scott Garman
2011-06-03 14:57 ` Koen Kooi
2011-06-09 11:02 ` Phil Blundell [this message]
2011-06-09 11:17 ` Richard Purdie
2011-06-09 15:00 ` Scott Garman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1307617330.2529.4803.camel@phil-desktop \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox