summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2016-07-07 14:27:43 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-07-08 09:57:27 +0100
commitb30125166836f93f24bd20ed09547cd54db5ed58 (patch)
treef39097ac85095a8ffa5320aeb83288a53ead6460
parent1b5688e0f0331ab9196cc534dabcade831a9090c (diff)
downloadpoky-b30125166836f93f24bd20ed09547cd54db5ed58.tar.gz
bitbake: progress: Ensure missing start event is fired
The init function of the parent class fires a progress event for 0 progress rather than a start event. UI code was assuming that progress events should always have a start event first. This change ensures that the start event is correctly generated. This fixes crashes that were seen in knotty in some configurations. (Bitbake rev: 9841651e050a3e9f395ab3c62545c51197734584) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--bitbake/lib/bb/progress.py3
1 files changed, 3 insertions, 0 deletions
diff --git a/bitbake/lib/bb/progress.py b/bitbake/lib/bb/progress.py
index 49417761bb..ee6b9536b8 100644
--- a/bitbake/lib/bb/progress.py
+++ b/bitbake/lib/bb/progress.py
@@ -209,6 +209,9 @@ class MultiStageProcessProgressReporter(MultiStageProgressReporter):
209 bb.event.fire(bb.event.ProcessStarted(self._processname, 100), self._data) 209 bb.event.fire(bb.event.ProcessStarted(self._processname, 100), self._data)
210 210
211 def _fire_progress(self, taskprogress): 211 def _fire_progress(self, taskprogress):
212 if taskprogress == 0:
213 self.start()
214 return
212 bb.event.fire(bb.event.ProcessProgress(self._processname, taskprogress), self._data) 215 bb.event.fire(bb.event.ProcessProgress(self._processname, taskprogress), self._data)
213 216
214 def finish(self): 217 def finish(self):