From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH v2 00/10] Support progress reporting
Date: Thu, 23 Jun 2016 22:59:02 +1200 [thread overview]
Message-ID: <cover.1466679280.git.paul.eggleton@linux.intel.com> (raw)
Add code to support progress reporting within OpenEmbedded, as well as a
couple of related changes to allow reworking the extensible SDK
installation process. (See the corresponding OE-Core series for further
details).
Changes since v1:
* Rebase on top of recent runqueue changes
* Fix debug=True in MultiStageProgressReporter printing weightings if
finish() was called a second time (as it is in the runqueue).
* Fix a couple of bugs with the BB_SETSCENE_ENFORCE code
* Add comments in the runqueue code explaining how to update the weightings
The following changes since commit 31977e7bb98f676197c6cee66f6ab4c12d4dcbde:
cooker: clean up EvertWriter (2016-06-20 17:23:53 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/startup-bb
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/startup-bb
Paul Eggleton (10):
knotty: provide a symlink to the latest console log
knotty: import latest python-progressbar
lib: implement basic task progress support
lib/bb/progress: add MultiStageProgressReporter
fetch2: implement progress support
knotty: add code to support showing progress for sstate object
querying
knotty: show task progress bar
knotty: add quiet output mode
runqueue: add ability to enforce that tasks are setscened
runqueue: report progress for "Preparing RunQueue" step
lib/bb/build.py | 34 ++++
lib/bb/event.py | 27 +++
lib/bb/fetch2/__init__.py | 4 +-
lib/bb/fetch2/git.py | 52 +++++-
lib/bb/fetch2/wget.py | 26 ++-
lib/bb/main.py | 9 +
lib/bb/msg.py | 5 +-
lib/bb/progress.py | 270 ++++++++++++++++++++++++++++
lib/bb/runqueue.py | 151 +++++++++++++++-
lib/bb/ui/knotty.py | 143 ++++++++++++---
lib/bb/ui/uihelper.py | 7 +-
lib/progressbar.py | 384 ----------------------------------------
lib/progressbar/LICENSE.txt | 52 ++++++
lib/progressbar/__init__.py | 49 ++++++
lib/progressbar/compat.py | 44 +++++
lib/progressbar/progressbar.py | 315 +++++++++++++++++++++++++++++++++
lib/progressbar/widgets.py | 391 +++++++++++++++++++++++++++++++++++++++++
17 files changed, 1542 insertions(+), 421 deletions(-)
create mode 100644 lib/bb/progress.py
delete mode 100644 lib/progressbar.py
create mode 100644 lib/progressbar/LICENSE.txt
create mode 100644 lib/progressbar/__init__.py
create mode 100644 lib/progressbar/compat.py
create mode 100644 lib/progressbar/progressbar.py
create mode 100644 lib/progressbar/widgets.py
--
2.5.5
next reply other threads:[~2016-06-23 10:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 10:59 Paul Eggleton [this message]
2016-06-23 10:59 ` [PATCH v2 01/10] knotty: provide a symlink to the latest console log Paul Eggleton
2016-06-23 10:59 ` [PATCH v2 02/10] knotty: import latest python-progressbar Paul Eggleton
2016-06-23 10:59 ` [PATCH v2 03/10] lib: implement basic task progress support Paul Eggleton
2016-06-23 10:59 ` [PATCH v2 04/10] lib/bb/progress: add MultiStageProgressReporter Paul Eggleton
2016-06-23 10:59 ` [PATCH v2 05/10] fetch2: implement progress support Paul Eggleton
2016-07-06 4:26 ` [PATCH v3] " Paul Eggleton
2016-07-10 22:23 ` Paul Eggleton
2016-07-10 22:25 ` Paul Eggleton
2016-06-23 10:59 ` [PATCH v2 06/10] knotty: add code to support showing progress for sstate object querying Paul Eggleton
2016-06-23 10:59 ` [PATCH v2 07/10] knotty: show task progress bar Paul Eggleton
2016-06-23 10:59 ` [PATCH v2 08/10] knotty: add quiet output mode Paul Eggleton
2016-06-23 10:59 ` [PATCH v2 09/10] runqueue: add ability to enforce that tasks are setscened Paul Eggleton
2016-06-23 10:59 ` [PATCH v2 10/10] runqueue: report progress for "Preparing RunQueue" step Paul Eggleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1466679280.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.