From: Jiajun Xu <jiajun.xu@intel.com>
To: poky@pokylinux.org
Subject: [PATCH 0/1] qemuimagetest: Use same image during sanity testing
Date: Wed, 19 Jan 2011 0:36:29 +0800 [thread overview]
Message-ID: <cover.1295368476.git.jiajun.xu@intel.com> (raw)
To reduce the time on sanity testing, we remove variable SHARE_IMAGE and use
a new variable TEST_SERIALIZE in local.conf. It is by default set to 1. Poky
will copy and boot the to-be tested image for only once. It will not remove
or kill the image and test cases will be serialized executed against the same
image. If it is set to 0, image is always be copied for each cases, which takes
much time. I had a experiment that latest qemuppc sato only takes 7 minutes to
finish 9 sanity test cases, which takes more than 20 minutes before.
I also removed sanity case "boot" for target sato/sdk/lsb because the other cases for
these targets already cover the check point of "boot".
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: jxu49/master
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=jxu49/master
Thanks,
Jiajun Xu <jiajun.xu@intel.com>
---
Jiajun Xu (1):
qemuimagetest: Use same image during sanity testing instead of
copying a new image for each case
meta/classes/imagetest-qemu.bbclass | 33 +++++-
meta/conf/local.conf.sample | 10 +-
scripts/qemuimage-testlib | 110 ++++++++++++++------
scripts/qemuimage-tests/sanity/compiler | 2 +-
scripts/qemuimage-tests/sanity/connman | 2 +-
scripts/qemuimage-tests/sanity/dmesg | 2 +-
scripts/qemuimage-tests/sanity/rpm_query | 2 +-
scripts/qemuimage-tests/sanity/scp | 2 +-
scripts/qemuimage-tests/sanity/shutdown | 11 +-
scripts/qemuimage-tests/sanity/ssh | 2 +-
scripts/qemuimage-tests/sanity/zypper_help | 2 +-
scripts/qemuimage-tests/sanity/zypper_search | 2 +-
.../scenario/qemuarm/poky-image-lsb | 3 +-
.../scenario/qemuarm/poky-image-sato | 3 +-
.../scenario/qemuarm/poky-image-sdk | 3 +-
.../scenario/qemumips/poky-image-lsb | 3 +-
.../scenario/qemumips/poky-image-sato | 3 +-
.../scenario/qemumips/poky-image-sdk | 3 +-
.../scenario/qemuppc/poky-image-lsb | 3 +-
.../scenario/qemuppc/poky-image-sato | 3 +-
.../scenario/qemuppc/poky-image-sdk | 3 +-
.../scenario/qemux86-64/poky-image-lsb | 3 +-
.../scenario/qemux86-64/poky-image-sato | 3 +-
.../scenario/qemux86-64/poky-image-sdk | 3 +-
.../scenario/qemux86/poky-image-lsb | 3 +-
.../scenario/qemux86/poky-image-sato | 3 +-
.../scenario/qemux86/poky-image-sdk | 3 +-
27 files changed, 138 insertions(+), 87 deletions(-)
next reply other threads:[~2011-01-18 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 16:36 Jiajun Xu [this message]
2011-01-18 16:36 ` [PATCH 1/1] qemuimagetest: Use same image during sanity testing instead of copying a new image for each case Jiajun Xu
2011-01-21 1:04 ` [PATCH 0/1] qemuimagetest: Use same image during sanity testing Saul Wold
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.1295368476.git.jiajun.xu@intel.com \
--to=jiajun.xu@intel.com \
--cc=poky@pokylinux.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.