From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] oe-build-perf-test: remove inter-dependencies of tests
Date: Fri, 26 Aug 2016 10:33:07 +0300 [thread overview]
Message-ID: <1472196791-24336-1-git-send-email-markus.lehtonen@linux.intel.com> (raw)
This patchset gets rid of the dependencies between tests. This should make the
results coherent even if some tests fail, and, make it practical to run only a
subset of tests with --run-tests.
The following changes since commit 00027aee12f4bbc9a4ba607c91fcc1e0e8257fa2:
core-image-kernel-dev.bb: Standardize use of _append and leading space. (2016-08-25 23:03:26 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib marquiz/buildperf/isolate-tests
http://git.openembedded.org/openembedded-core-contrib/log/?h=marquiz/buildperf/isolate-tests
Markus Lehtonen (4):
oeqa.buildperf: fix checking of invalid results
oeqa.buildperf: make tests independent
oeqa.buildperf: treat failed measurements as errors
oe-build-perf-test: update globalres and git even if tests failed
meta/lib/oeqa/buildperf/base.py | 45 ++++++++++++++++-------------------
meta/lib/oeqa/buildperf/test_basic.py | 10 +++++---
scripts/oe-build-perf-test | 12 +++++-----
3 files changed, 34 insertions(+), 33 deletions(-)
--
2.6.6
next reply other threads:[~2016-08-26 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 7:33 Markus Lehtonen [this message]
2016-08-26 7:33 ` [PATCH 1/4] oeqa.buildperf: fix checking of invalid results Markus Lehtonen
2016-08-26 7:33 ` [PATCH 2/4] oeqa.buildperf: make tests independent Markus Lehtonen
2016-08-26 7:33 ` [PATCH 3/4] oeqa.buildperf: treat failed measurements as errors Markus Lehtonen
2016-08-26 7:33 ` [PATCH 4/4] oe-build-perf-test: update globalres and git even if tests failed 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=1472196791-24336-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