From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52152) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHtj3-0005Nd-SF for qemu-devel@nongnu.org; Tue, 28 Jun 2016 10:10:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bHtix-00039V-2Y for qemu-devel@nongnu.org; Tue, 28 Jun 2016 10:10:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48411) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHtiw-00039R-Sp for qemu-devel@nongnu.org; Tue, 28 Jun 2016 10:10:46 -0400 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 574351176A9 for ; Tue, 28 Jun 2016 14:10:46 +0000 (UTC) Date: Tue, 28 Jun 2016 16:10:44 +0200 From: Kevin Wolf Message-ID: <20160628141044.GH6800@noname.redhat.com> References: <20160628090209.GD10557@ndevos-x240.usersys.redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rS8CxjVDS/+yyDmU" Content-Disposition: inline In-Reply-To: <20160628090209.GD10557@ndevos-x240.usersys.redhat.com> Subject: Re: [Qemu-devel] Automated testing of block/gluster.c with upstream Gluster List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Niels de Vos , ldoktor@redhat.com, areis@redhat.com Cc: qemu-devel@nongnu.org --rS8CxjVDS/+yyDmU Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Am 28.06.2016 um 11:02 hat Niels de Vos geschrieben: > Hi, >=20 > 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. >=20 > 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=C3=A1=C5=A1 who probably can (and I= think it shouldn't be hard anyway). Kevin --rS8CxjVDS/+yyDmU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJXcoVkAAoJEH8JsnLIjy/WKCcQAML+fjdNHvVpZZHhPwcwy8Mg emlA3J/hptYerQV+of9BbYxjxrJ/icwJETe4oF1abTMdKCpIhNrKvFc9JSZgqfxO cng4pALq72eoe0OU3COxXZTZTIXRe6+kZN5qXJIuqIroYzOoXRkoM0IXmGbirbGt r26K6snQ33v8alcvCLGE29i6ID0Oco1ZwoD0Msgptwy/LLrxBmhtrlx4jxXnuEZN 2c7svTgvjLQtQDTaqHRhq8oS4o6HnQw4QEgD6JfWCGmv8AcOCEfQ+ixWcxPKuADn QMLiBnXzSdfbZ0Ip5avXB+WI1s5c7ERX649DMyRfUn6J/WfMkOOQPrZhnrigOJLz X2lTkEaLrAHNoyVIAjN7ncu8UZBuBZ4dCsztkCWMDKZh9QrfjhD/VqZTTEQUKWzQ PBo8O4HRxAWJSaOg03fjYY+vK4FjAICIjAo5k0SAMWnROGes/WVIrh0xZdFNNLjg Cn3evn4s3980jtpwdo1hC9KAFQzGAh3pY0f+XtjSj3qYHzFT/4TXwi32I7/GyWPm wnl21BG1tVg2ZcNrmyUD6+hvDl5cgJbxNiAi6/TdlksGYqYlP7Wc4kjfAkcYwEt0 1bC5650yXWIFoWbx+6Km1ip+WVj9UXuZTHkzdLKKbmtZuwkmH5+Jdaw6hQOF1ykk wTG/OSWrN1rBCXMFvRdo =7e3R -----END PGP SIGNATURE----- --rS8CxjVDS/+yyDmU--