From: Martin Jansa <martin.jansa@gmail.com>
To: bitbake-devel@lists.openembedded.org
Subject: Interesting typo with a bit confusing python exception
Date: Sat, 9 Aug 2014 11:49:32 +0200 [thread overview]
Message-ID: <20140809094932.GL14848@jama> (raw)
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
Don't take this as bug report, the first ERROR message is right
and I should have noticed what's wrong sooner, but instead I was
checking "ps" for hanging zombie bitbake (which still happends
from time to time).
Is there something we can do for average bitbake user to get clearer
message?
$ bitbake -c cleansstate tracker | bitbake -c build tracker | tee log.tracker
ERROR: Only one copy of bitbake should be run against a build directory
Traceback (most recent call last):
File "/OE/build/oe-core/bitbake/bin/bitbake", line 382, in <module>
ret = main()
File "/OE/build/oe-core/bitbake/bin/bitbake", line 370, in main
return ui_module.main(server_connection.connection, server_connection.events, configParams)
File "/OE/build/oe-core/bitbake/lib/bb/ui/knotty.py", line 396, in main
parseprogress.update(event.current)
AttributeError: 'NoneType' object has no attribute 'update'
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
reply other threads:[~2014-08-09 9:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140809094932.GL14848@jama \
--to=martin.jansa@gmail.com \
--cc=bitbake-devel@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