From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] Enhancements to build perf reporting
Date: Mon, 15 May 2017 14:18:40 +0300 [thread overview]
Message-ID: <cover.1494846894.git.markus.lehtonen@linux.intel.com> (raw)
This patchset contains a bug fix and two new features for the
oe-build-perf-report script. There's also a patch to to the buildstats-diff
script for analyzing the JSON-based buildstats from build performance test
reports.
The following changes since commit c59fa3bd71b42410bf032846ee8fdb6e6eb1b95c:
python*-git: Upgrade to version 2.1.3 (2017-05-12 08:49:30 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib marquiz/fixes-11355
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=marquiz/fixes-11355
Markus Lehtonen (5):
oeqa.utils.git: use --verify in rev_parse()
oe-build-perf-report: use correct x-axis max value in html charts
oe-build-perf-report: two verbosity levels for --list
oe-build-perf-report: implement --dump-buildstats
scripts/buildstats-diff: support optimized rusage values
meta/lib/oeqa/utils/git.py | 2 +-
scripts/buildstats-diff | 20 +++++++--
scripts/oe-build-perf-report | 96 +++++++++++++++++++++++++++++++++++++-------
3 files changed, 99 insertions(+), 19 deletions(-)
--
2.12.0
next reply other threads:[~2017-05-15 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 11:18 Markus Lehtonen [this message]
2017-05-15 11:18 ` [PATCH 1/5] oeqa.utils.git: use --verify in rev_parse() Markus Lehtonen
2017-05-15 11:18 ` [PATCH 2/5] oe-build-perf-report: use correct x-axis max value in html charts Markus Lehtonen
2017-05-15 11:18 ` [PATCH 3/5] oe-build-perf-report: two verbosity levels for --list Markus Lehtonen
2017-05-15 11:18 ` [PATCH 4/5] oe-build-perf-report: implement --dump-buildstats Markus Lehtonen
2017-05-15 11:18 ` [PATCH 5/5] scripts/buildstats-diff: support optimized rusage values Markus Lehtonen
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.1494846894.git.markus.lehtonen@linux.intel.com \
--to=markus.lehtonen@linux.intel.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox