From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34827) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHouP-0006tz-IC for qemu-devel@nongnu.org; Tue, 28 Jun 2016 05:02:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bHouK-0003OU-Vy for qemu-devel@nongnu.org; Tue, 28 Jun 2016 05:02:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36561) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHouK-0003OM-QW for qemu-devel@nongnu.org; Tue, 28 Jun 2016 05:02:12 -0400 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (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 C1AB23D1F7 for ; Tue, 28 Jun 2016 09:02:11 +0000 (UTC) Received: from localhost (ovpn-116-106.ams2.redhat.com [10.36.116.106]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u5S92AFN015473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 28 Jun 2016 05:02:11 -0400 Date: Tue, 28 Jun 2016 11:02:09 +0200 From: Niels de Vos Message-ID: <20160628090209.GD10557@ndevos-x240.usersys.redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline Subject: [Qemu-devel] Automated testing of block/gluster.c with upstream Gluster List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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/ --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXcj0RAAoJECXo5AApwsWzJP0P/1Q7anm8Ne05LlE1/HekOwdX xUIlKR4w7JO+8p8Mh7E4Jj2mTxN3UcjdzMmjnT6QJWaPvm2SRvF68HfaOXwao7SU kRd31OcFSFOF7iUBszb+BfFGYeSBLId0ZTJm7ujg+n5XshCMQPChhGLSajS2dExK 5+hQbz4O+ZVwrFELsPD8SjdHTfzegVV7GI4TInhJsIj1pJBh2PNYEOtKqjnaPTg3 fP4xNu1ey2868y2dITRRcpkO+dhFgvGb2mkfnS91VtiMFZy4osICnEVsLjU3yD4B 0PQP6n4wyMj4PV6tNzVOG+20UjLUPiCg+Zw2SrLYLpMTyLhjF2gkkJWgLlTjKdk7 t49eEjVV9SVrvoat/VMUtS6ePJx0jxqNSMLKO8le5nlTVGBu20FXc0Q8I/TW9hsc DFtXYx/Quf2J0UA9+Y3QhHwzNQ+Q9hlcVJa2Dtu9IdKZqX9PLmCzT8a8TqLXmC+j kC4RI7Jhb1MUbh6X/tJQ7wOhD2GLpNZ7MvVRKECfsxCLRATodswFXGo75rBUdq5Y Bhc1rFWi8GdQfUV3BjJ8uC//hiq0q9eTSllCtxlBWOlRX2ALg2TUmZu9SeWBxQgQ W//P+ORO+VKEp1g0kAqVFIf1cuI6odwBXETJ2pNPw+X0g9zqvtS6r1idlyOzCURs aC4eiY/FH+Pk03QBjq7o =oiVV -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl--