From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45210) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHuo8-0007cK-FS for qemu-devel@nongnu.org; Tue, 28 Jun 2016 11:20:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bHuo4-0004qk-AZ for qemu-devel@nongnu.org; Tue, 28 Jun 2016 11:20:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:44300) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHuo4-0004pK-37 for qemu-devel@nongnu.org; Tue, 28 Jun 2016 11:20:08 -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 1A6916315E for ; Tue, 28 Jun 2016 15:20:07 +0000 (UTC) References: <20160628090209.GD10557@ndevos-x240.usersys.redhat.com> <20160628141044.GH6800@noname.redhat.com> From: =?UTF-8?B?THVrw6HFoSBEb2t0b3I=?= Message-ID: <72a6e933-55fc-f448-a0bc-3861b030b73c@redhat.com> Date: Tue, 28 Jun 2016 17:20:03 +0200 MIME-Version: 1.0 In-Reply-To: <20160628141044.GH6800@noname.redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Ji6vAW5TeW6kjTe3XccaRBmpFruNL05wH" 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: Kevin Wolf , Niels de Vos , areis@redhat.com Cc: qemu-devel@nongnu.org, Xu Tian , Hao Liu This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Ji6vAW5TeW6kjTe3XccaRBmpFruNL05wH From: =?UTF-8?B?THVrw6HFoSBEb2t0b3I=?= To: Kevin Wolf , Niels de Vos , areis@redhat.com Cc: qemu-devel@nongnu.org, Xu Tian , Hao Liu Message-ID: <72a6e933-55fc-f448-a0bc-3861b030b73c@redhat.com> Subject: Re: [Qemu-devel] Automated testing of block/gluster.c with upstream Gluster References: <20160628090209.GD10557@ndevos-x240.usersys.redhat.com> <20160628141044.GH6800@noname.redhat.com> In-Reply-To: <20160628141044.GH6800@noname.redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Dne 28.6.2016 v 16:10 Kevin Wolf napsal(a): > 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 patc= h >> 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 CentO= S >> 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 so= me >> 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 (a= nd I think > it shouldn't be hard anyway). > > Kevin > Hello guys, yes, Avocado is designed to do this and I believe it even contain quite=20 a few Gluster tests. You can look for them in avocado-vt or ping our QA=20 folks who might give you some pointers (cc Xu nad Hao). Regarding the building the CI I use the combination of Jenkins, Jenkins=20 job builder and Avocado (avocado-vt) to check power/arm=20 weekly/per-package-update. Jenkins even supports github and other=20 triggers if you decide you have enough resources to check each=20 PR/commit. It all depends on what HW you have available. Regards, Luk=C3=A1=C5=A1 --Ji6vAW5TeW6kjTe3XccaRBmpFruNL05wH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXcpWjAAoJECazYuR/zyLBizMIAIw9XPJUm64sjR9UfnGWBRF0 ZXQR7Nq3IKJ472kJbwVxyvPb09fALZrF6e648GunzXCHVElmRwbbvot6lVQUKrkL M5i+oWYVC+2CoAIKSH+3zzK1cR0PvfvVvv1Rxtmt70qzGoW2Oncan4zcQDYPBSRt 51pBlpSZ1UzpfLnUsIMouxyeBmvolnw4Z0dWpb74y6d7MMBw0iUMM6l0kvPbMzzH rok31TfaQJUEr2omdG1P4JvY9SeaX/Vy7fYB67fQkTl72IVlQ5NBHQb7fOn3+A90 UMA/LmUPgef1ekWUHNyGHmlqEpy4SfUmndQho9eKAlySNb1x8H14xOKXlZtkqvI= =ojvf -----END PGP SIGNATURE----- --Ji6vAW5TeW6kjTe3XccaRBmpFruNL05wH--