From ead05456264e9c7c32819271562d0ac074ecaee3 Mon Sep 17 00:00:00 2001 From: Ed Bartosh Date: Mon, 5 Sep 2016 14:27:35 +0300 Subject: [PATCH] bitbake: cooker: record events on cooker exit Bitbake collects all events in special event queue when called with -w option. However, it starts to write events to the eventlog only after BuildStarted event is received. In some cases this event is not received at all, e.g. when bitbake is run with --parse-only command line option. It makes sense to write all collected events when CookerExit event received to make sure all events are written into the eventlog even if BuildStarted event is not fired. [YOCTO #10145] (Bitbake rev: 57912de63fa83550c0ae658eb99b76e9cc91a8d1) Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie --- bitbake/lib/bb/cooker.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bitbake/lib/bb/cooker.py b/bitbake/lib/bb/cooker.py index b7d7a7ec21..0e78106d29 100644 --- a/bitbake/lib/bb/cooker.py +++ b/bitbake/lib/bb/cooker.py @@ -141,7 +141,7 @@ class EventWriter: else: # init on bb.event.BuildStarted name = "%s.%s" % (event.__module__, event.__class__.__name__) - if name == "bb.event.BuildStarted": + if name in ("bb.event.BuildStarted", "bb.cooker.CookerExit"): with open(self.eventfile, "w") as f: f.write("%s\n" % json.dumps({ "allvariables" : self.cooker.getAllKeysWithFlags(["doc", "func"])}))