summaryrefslogtreecommitdiffstats
path: root/bitbake
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2015-06-25 17:53:23 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-06-29 09:49:12 +0100
commit58b038b7783b32aeb8ee138728b6d801dacd7da4 (patch)
tree9ea7c70f81e63ced9aa20f04cd8af184e017ec3b /bitbake
parentf6430d42b4c8f5e480ea53a5e02a2c212c0f7559 (diff)
downloadast2050-yocto-poky-58b038b7783b32aeb8ee138728b6d801dacd7da4.zip
ast2050-yocto-poky-58b038b7783b32aeb8ee138728b6d801dacd7da4.tar.gz
bitbake: cooker: Fire BuildCompleted before finishing the command
Some handlers hook on BuildComplete so it avoids certain event races to finish the command after the BuildComplete event is sent out. This means the UI is available to handle events until the command completes. What appears to be a race on one of the sanity tests for event handlers triggered this change although the failure is hard to reproduce. [YOCTO #7921] (Bitbake rev: ac66fac162e68b568f986fe1917772e61c982f8e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake')
-rw-r--r--bitbake/lib/bb/cooker.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/bitbake/lib/bb/cooker.py b/bitbake/lib/bb/cooker.py
index 9c101f2..f32dae0 100644
--- a/bitbake/lib/bb/cooker.py
+++ b/bitbake/lib/bb/cooker.py
@@ -1303,8 +1303,8 @@ class BBCooker:
return False
if not retval:
- self.command.finishAsyncCommand(msg)
bb.event.fire(bb.event.BuildCompleted(len(rq.rqdata.runq_fnid), buildname, item, failures), self.expanded_data)
+ self.command.finishAsyncCommand(msg)
return False
if retval is True:
return True
@@ -1336,8 +1336,8 @@ class BBCooker:
return False
if not retval:
- self.command.finishAsyncCommand(msg)
bb.event.fire(bb.event.BuildCompleted(len(rq.rqdata.runq_fnid), buildname, targets, failures), self.data)
+ self.command.finishAsyncCommand(msg)
return False
if retval is True:
return True
OpenPOWER on IntegriCloud