* [PATCH] bin/bitbake-worker: Fix invalid bb.msg.fatal usage
@ 2016-05-11 21:57 Richard Purdie
0 siblings, 0 replies; only message in thread
From: Richard Purdie @ 2016-05-11 21:57 UTC (permalink / raw)
To: bitbake-devel
The logging domain specified to bb.msg.fatal was invalid. Replace with
a logger.critical() call instead.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
diff --git a/bitbake/bin/bitbake-worker b/bitbake/bin/bitbake-worker
index a4e8914..eb80306 100755
--- a/bitbake/bin/bitbake-worker
+++ b/bitbake/bin/bitbake-worker
@@ -159,7 +159,7 @@ def fork_off_task(cfg, data, workerdata, fn, task, taskname, appends, taskdepdat
pipeout = os.fdopen(pipeout, 'wb', 0)
pid = os.fork()
except OSError as e:
- bb.msg.fatal("RunQueue", "fork failed: %d (%s)" % (e.errno, e.strerror))
+ logger.critical("fork failed: %d (%s)" % (e.errno, e.strerror))
if pid == 0:
def child():
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2016-05-11 22:06 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-05-11 21:57 [PATCH] bin/bitbake-worker: Fix invalid bb.msg.fatal usage Richard Purdie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox