From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>,
<richard.purdie@linuxfoundation.org>,
<paul.eggleton@linux.intel.com>, <ross.burton@intel.com>
Subject: [RFC PATCH 0/5] revive runtime/cases/_ptest.py
Date: Wed, 19 Jul 2017 01:16:04 -0700 [thread overview]
Message-ID: <cover.1500450690.git.liezhi.yang@windriver.com> (raw)
Hello,
These patches can make ptest test case work, RP has suggested we write a tool to
do the regression check on ptest result, I think that the use case is like:
$ bitbake <image> -ctestiamge # Suppose we add ptest to default test cases in the future
# Upgrade a recipe form V1.0 to V1.1
$ bitbake <image> -ctestiamge # Run the test again
Then the regression check tool can report what's different (passed, failed,
skipped) between V1.0 and V1.1.
Currently, I'm not sure about where to save the ptest results, I saved it to
${WORKDIR}/testimage/ptest_log atm, e.g.:
tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage/ptest_log
But it will be removed after -cclean, then no regression check can be made, so
I'd like to save the ptest results to DEPLOY_DIR_IMAGE if no objections, and
make -cclean not remove them. (Or only keep the latest 2 results).
And I'm not sure where to add the regression check/tool, maybe one of:
1) Add a separate tool in oe-core/scripts, this can make it easy to do regression
check among different build directories, and runtime/cases/_ptest.py can invoke it.
2) Add it to runtime/cases/_ptest.py directly
3) Add it to buildhistory
I prefer the first one, please feel free to give your comments.
// Robert
The following changes since commit ef68005a8c527e9b1d05b7769f0ec8ebe9ec3f91:
webkitgtk: Upgrade to 2.16.5 (2017-07-17 13:49:04 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/ptest
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/ptest
Robert Yang (5):
oeqa/targetcontrol.py: simplify checking for qemu_use_kvm
runtime/cases/_ptest.py: revive it
oeqa/utils/logparser.py: add skip status
runtime/cases/_ptest.py: add skip status
runtime/cases/_ptest.py: rename it to ptest.py
meta/lib/oeqa/runtime/cases/_ptest.py | 103 ----------------------------------
meta/lib/oeqa/runtime/cases/ptest.py | 77 +++++++++++++++++++++++++
meta/lib/oeqa/targetcontrol.py | 5 +-
meta/lib/oeqa/utils/logparser.py | 5 +-
4 files changed, 82 insertions(+), 108 deletions(-)
delete mode 100644 meta/lib/oeqa/runtime/cases/_ptest.py
create mode 100644 meta/lib/oeqa/runtime/cases/ptest.py
--
2.11.0
next reply other threads:[~2017-07-19 8:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 8:16 Robert Yang [this message]
2017-07-19 8:16 ` [RFC PATCH 1/5] oeqa/targetcontrol.py: simplify checking for qemu_use_kvm Robert Yang
2017-07-19 8:16 ` [RFC PATCH 2/5] runtime/cases/_ptest.py: revive it Robert Yang
2017-07-19 8:16 ` [RFC PATCH 3/5] oeqa/utils/logparser.py: add skip status Robert Yang
2017-07-19 8:16 ` [RFC PATCH 4/5] runtime/cases/_ptest.py: " Robert Yang
2017-07-19 8:16 ` [RFC PATCH 5/5] runtime/cases/_ptest.py: rename it to ptest.py Robert Yang
2017-07-20 2:09 ` [RFC PATCH 0/5] revive runtime/cases/_ptest.py Robert Yang
2017-07-21 12:32 ` Richard Purdie
2017-07-24 2:11 ` Robert Yang
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.1500450690.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@intel.com \
/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