diff options
| author |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-07-07 14:27:43 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-07-08 09:57:06 +0100 |
| commit | 9841651e050a3e9f395ab3c62545c51197734584 (patch) | |
| tree | 5442b29c1d7654e99187251971af64fbd21561bf | |
| parent | 7dd06b1016b36420a9c55a45ff29dd64ae1dbcda (diff) | |
| download | bitbake-contrib-9841651e050a3e9f395ab3c62545c51197734584.tar.gz | |
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.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | lib/bb/progress.py | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/lib/bb/progress.py b/lib/bb/progress.py index 49417761b..ee6b9536b 100644 --- a/lib/bb/progress.py +++ b/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): |