[poky] Duplicated error messages

Chris Larson clarson at kergoth.com
Thu Jun 2 07:32:01 PDT 2011


On Thu, Jun 2, 2011 at 7:22 AM, Gary Thomas <gary at mlbassoc.com> wrote:
>> This is my fault -- at least, the continuing on is. As a part of
>> working on improving the exception handling in bitbake, the behavior
>> of exceptions in event handlers was changed.  We should likely change
>> it back for the SystemExit case, or add a more explicit method for
>> event handlers to communicate with bitbake proper. Sorry about that.
>
> Thanks.  Even if this is not the desired behaviour (bitbake used to just
> quit
> at the start when this happened), it is pointing out two other problems;
> the duplicated error messages (I'd look for why this happens, but I really
> wouldn't know where to start) and the less than helpful Python traceback.

Indeed, regardless those should go on the ever growing list of ugly
error message issues :) I suspect at least some of the error
duplications which have been reported are caused by the fact that
python tasks both emit their messages directly to the user (not the
case for shell tasks, obviously), and to their log file, and the log
file is then shown to the user on failure. For the python case, either
the task shouldn't be able to output directly to the user, or we
shouldn't show their log on failure, I suspect.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics



More information about the poky mailing list