Poky Project Discussions
 help / color / mirror / Atom feed
From: Jiajun Xu <jiajun.xu@intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/1] qemuimagetest: Use the same image in sanity testing to fix the timeout issue on autobuilder
Date: Thu, 13 Jan 2011  9:50:06 +0800	[thread overview]
Message-ID: <cover.1294883271.git.jiajun.xu@intel.com> (raw)

Fixes [BUGID #595]

Because of the QEMU booting slowness issue(see bug #646 and #618), autobuilder
is suffering a timeout issue when running sanity test. We introduce variable
SHARE_IMAGE here to fix the issue. It is by default set to 1. Poky will copy
latest built-out image and keep using it in sanity testing. If it is set to 0,
latest built-out image will be copied and tested for each case, which will take
much time.

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 the same image in sanity testing to fix the
    timeout issue on autobuilder

 meta/classes/imagetest-qemu.bbclass                |   22 +++++++++++++++++--
 meta/conf/local.conf.sample                        |    8 +++++++
 scripts/qemuimage-testlib                          |    7 ++++++
 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            |    7 +++++-
 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                |    2 +-
 .../scenario/qemuarm/poky-image-sato               |    2 +-
 .../scenario/qemuarm/poky-image-sdk                |    2 +-
 .../scenario/qemumips/poky-image-lsb               |    2 +-
 .../scenario/qemumips/poky-image-sato              |    2 +-
 .../scenario/qemumips/poky-image-sdk               |    2 +-
 .../scenario/qemuppc/poky-image-lsb                |    2 +-
 .../scenario/qemuppc/poky-image-sato               |    2 +-
 .../scenario/qemuppc/poky-image-sdk                |    2 +-
 .../scenario/qemux86-64/poky-image-lsb             |    2 +-
 .../scenario/qemux86-64/poky-image-sato            |    2 +-
 .../scenario/qemux86-64/poky-image-sdk             |    2 +-
 .../scenario/qemux86/poky-image-lsb                |    2 +-
 .../scenario/qemux86/poky-image-sato               |    2 +-
 .../scenario/qemux86/poky-image-sdk                |    2 +-
 27 files changed, 63 insertions(+), 27 deletions(-)



             reply	other threads:[~2011-01-13  1:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13  1:50 Jiajun Xu [this message]
2011-01-13  1:50 ` [PATCH 1/1] qemuimagetest: Use the same image in sanity testing to fix the timeout issue on autobuilder Jiajun Xu
2011-01-20 23:26 ` [PATCH 0/1] " 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.1294883271.git.jiajun.xu@intel.com \
    --to=jiajun.xu@intel.com \
    --cc=poky@yoctoproject.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