qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Niels de Vos <ndevos@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Automated testing of block/gluster.c with upstream Gluster
Date: Tue, 28 Jun 2016 11:02:09 +0200	[thread overview]
Message-ID: <20160628090209.GD10557@ndevos-x240.usersys.redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

Hi,

it seems we broke the block/gluster.c functionality with a recent patch
in upstream Gluster. In order to prevent this from happening in the
future, I would like to setup a Jenkins job that installs a plan CentOS
with its version of QEMU, and nightly builds of upstream Gluster.
Getting a notification about breakage the day after a patch got merged
seems like a reasonable approach.

The test should at least boot the generic CentOS cloud image (slightly
modified with libguestfs) and return a success/fail. I am wondering if
there are automated tests like this already, and if I could (re)use some
of the scripts for it. At the moment, I am thinking to so it like this:
 - download the image [1]
 - set kernel parameters to output on the serial console
 - add a auto-login user/script
 - have the script write "bootup complete" or something
 - have the script poweroff the VM
 - script that started the VM checks for the "bootup complete" message
 - return success/fail

Ideas and suggestions for running more heavy I/O in the VM are welcome
too.

Thanks,
Niels


1. http://cloud.centos.org/centos/7/images/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-06-28  9:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  9:02 Niels de Vos [this message]
2016-06-28  9:41 ` [Qemu-devel] Automated testing of block/gluster.c with upstream Gluster Vasiliy Tolstov
2016-06-28 10:27   ` Niels de Vos
2016-06-28 10:54     ` Vasiliy Tolstov
2016-06-28 14:10 ` Kevin Wolf
2016-06-28 15:20   ` Lukáš Doktor
2016-06-28 15:56     ` Niels de Vos
2016-06-29  7:39       ` Lukáš Doktor
2016-06-29  9:55         ` Niels de Vos

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=20160628090209.GD10557@ndevos-x240.usersys.redhat.com \
    --to=ndevos@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).