From: Kevin Wolf <kwolf@redhat.com>
To: Niels de Vos <ndevos@redhat.com>, ldoktor@redhat.com, areis@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Automated testing of block/gluster.c with upstream Gluster
Date: Tue, 28 Jun 2016 16:10:44 +0200 [thread overview]
Message-ID: <20160628141044.GH6800@noname.redhat.com> (raw)
In-Reply-To: <20160628090209.GD10557@ndevos-x240.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
Am 28.06.2016 um 11:02 hat Niels de Vos geschrieben:
> 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
Sounds like something that Avocado should be able (or actually is
designed) to do. I can't tell you the details of how to write the test
case for it, but I'm adding a CC to Lukáš who probably can (and I think
it shouldn't be hard anyway).
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-06-28 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 9:02 [Qemu-devel] Automated testing of block/gluster.c with upstream Gluster Niels de Vos
2016-06-28 9:41 ` Vasiliy Tolstov
2016-06-28 10:27 ` Niels de Vos
2016-06-28 10:54 ` Vasiliy Tolstov
2016-06-28 14:10 ` Kevin Wolf [this message]
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=20160628141044.GH6800@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=areis@redhat.com \
--cc=ldoktor@redhat.com \
--cc=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).