From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/12] oe-build-perf-test: new format for test output data
Date: Mon, 29 Aug 2016 22:48:19 +0300 [thread overview]
Message-ID: <1472500111-12358-1-git-send-email-markus.lehtonen@linux.intel.com> (raw)
This patchset changes the structure and format of the test output data. The
goal is to make the test result format more consolidated and easier to consume.
The major change is that the test results are stored in JSON format, in
addition to the (optional) csv-formatted "globalres file". Also, buildstats are
converted into JSON.
This patchset is based on top of the earlier "test inter-dependency removal"
patchset for oe-build-perf-test.
[YOCTO #9625]
The following changes since commit 74a62a0a9e4758de4bd2d891f9a133f028e86913:
oe-build-perf-test: update globalres and git even if tests failed (2016-08-26 10:11:38 +0300)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib marquiz/buildperf/new-result-fmt
http://git.openembedded.org/openembedded-core-contrib/log/?h=marquiz/buildperf/new-result-fmt
Markus Lehtonen (12):
oeqa.buildperf: add 'product' to test result data
oeqa.buildperf: enable json-formatted results
oe-build-perf-test: rename log file and implement --log-file
oeqa.buildperf: strip date from buildstats directory path
oeqa.buildperf: separate output dir for each test
oeqa.buildperf: rename buildstats directories
oeqa.buildperf: don't use Gnu time
oeqa.buildperf: measure io stat
oeqa.buildperf: convert buildstats into json format
oeqa.buildperf: show skipped tests in results, too
oeqa.buildperf: include buildstats file name in results.json
oeqa.buildperf: include commands log file name in results.json
meta/lib/oeqa/buildperf/base.py | 228 +++++++++++++++++++++++++++-------
meta/lib/oeqa/buildperf/test_basic.py | 7 +-
scripts/oe-build-perf-test | 5 +-
3 files changed, 190 insertions(+), 50 deletions(-)
--
2.6.6
next reply other threads:[~2016-08-29 19:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 19:48 Markus Lehtonen [this message]
2016-08-29 19:48 ` [PATCH 01/12] oeqa.buildperf: add 'product' to test result data Markus Lehtonen
2016-08-29 19:48 ` [PATCH 02/12] oeqa.buildperf: enable json-formatted results Markus Lehtonen
2016-08-29 19:48 ` [PATCH 03/12] oe-build-perf-test: rename log file and implement --log-file Markus Lehtonen
2016-08-29 19:48 ` [PATCH 04/12] oeqa.buildperf: strip date from buildstats directory path Markus Lehtonen
2016-08-29 19:48 ` [PATCH 05/12] oeqa.buildperf: separate output dir for each test Markus Lehtonen
2016-08-29 19:48 ` [PATCH 06/12] oeqa.buildperf: rename buildstats directories Markus Lehtonen
2016-08-29 19:48 ` [PATCH 07/12] oeqa.buildperf: don't use Gnu time Markus Lehtonen
2016-08-29 19:48 ` [PATCH 08/12] oeqa.buildperf: measure io stat Markus Lehtonen
2016-08-29 19:48 ` [PATCH 09/12] oeqa.buildperf: convert buildstats into json format Markus Lehtonen
2016-08-29 19:48 ` [PATCH 10/12] oeqa.buildperf: show skipped tests in results, too Markus Lehtonen
2016-08-29 19:48 ` [PATCH 11/12] oeqa.buildperf: include buildstats file name in results.json Markus Lehtonen
2016-08-29 19:48 ` [PATCH 12/12] oeqa.buildperf: include commands log " 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=1472500111-12358-1-git-send-email-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