From b30125166836f93f24bd20ed09547cd54db5ed58 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Thu, 7 Jul 2016 14:27:43 +0100 Subject: 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 --- bitbake/lib/bb/progress.py | 3 +++ 1 file changed, 3 insertions(+) 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): bb.event.fire(bb.event.ProcessStarted(self._processname, 100), self._data) def _fire_progress(self, taskprogress): + if taskprogress == 0: + self.start() + return bb.event.fire(bb.event.ProcessProgress(self._processname, taskprogress), self._data) def finish(self): -- cgit v1.2.3-54-g00ecf