Paul Eggleton 4e8085ccfa bitbake/runqueue: avoid "failed" in task summary if nothing did ...

Seeing the word "failed" alone without reading the whole context has
occasionally triggered an automatic assumption on the part of some users
(myself included) that something has gone wrong, even when this message
is telling you that "0 [tasks] failed". To avoid this let's just say
"all succeeded" in this case instead.

As a bonus this means you can now search the output for "fail" and not
find anything if all went well.

(Bitbake rev: b6f067af12d4661758a78788f1db472684b9aba8)

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2012-01-15 10:06:21 +00:00

..

bb

bitbake/runqueue: avoid "failed" in task summary if nothing did

2012-01-15 10:06:21 +00:00

ply

Add pysh, ply, and codegen to lib/ to prepare for future work

2010-08-03 14:06:07 +01:00

prserv

bitbake: Automatically start local PR service.

2012-01-11 10:36:20 +00:00

codegen.py

Add pysh, ply, and codegen to lib/ to prepare for future work

2010-08-03 14:06:07 +01:00

progressbar.py

Experimental usage of the 'progressbar' module

2011-01-04 14:46:42 +00:00