From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=57118 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PmdL1-00024h-Ne for qemu-devel@nongnu.org; Mon, 07 Feb 2011 21:29:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PmdL0-00021I-JO for qemu-devel@nongnu.org; Mon, 07 Feb 2011 21:29:55 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40448) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PmdL0-00021A-Cl for qemu-devel@nongnu.org; Mon, 07 Feb 2011 21:29:54 -0500 From: Lucas Meneghel Rodrigues In-Reply-To: References: <9F3B6BB7-4256-4403-A8A8-F91368A98231@suse.de> Content-Type: text/plain; charset="UTF-8" Date: Tue, 08 Feb 2011 00:29:43 -0200 Message-ID: <1297132183.2738.17.camel@freedom> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: Buildbot for qemu.git/master List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Michael Tokarev , Alexander Graf , qemu-devel , Andreas =?ISO-8859-1?Q?F=E4rber?= , gollub@b1-systems.de On Mon, 2011-02-07 at 14:36 +0000, Stefan Hajnoczi wrote: > On Mon, Feb 7, 2011 at 1:00 PM, Alexander Graf wrote: > > > > On 05.02.2011, at 21:32, Stefan Hajnoczi wrote: > > > >> Here is the buildbot. It currently has a debian-x86_64 slave building > >> qemu.git/master every 24 hours: > >> http://buildbot.vmsplice.net/ > > > > This is great - thank you! I'll try to get some ppc and s390x VMs set up to run this. Do you have any plans to also integrate actual testing of the compiled code? > > Cool :). Yes testing can be added after build. Are there specific > automated tests you're thinking of? > > I plan to add qemu-iotests. > > Perhaps the kvm-autotest folks want to contribute a buildslave? I > have CCed Lucas Meneghel Rodrigues. I am not too familiar with buildbot myself, so I went to the buildbot page and read some of the documentation. KVM autotest has its own kvm build code, and we do run jobs that build qemu.git and run some sanity checking on it (ie, install some guest OSs and boot the vms, as well as other simple tests). If I understood correctly, a build slave is a machine where the compilation happens and then the build master can report appropriately upon failure/pass. The way the kvm autotest jobs are setup nowadays provides just that, an environment where the latest qemu-kvm.git and qemu.git are built on a timely basis (every 48 hours) and then the actual testing of the compiled code happens. Of course, maybe there's a way to trigger kvm autotest jobs upon successful buildbot builds, and if that is possible, I'd be happy to help setting up a test environment that'd accomplish public automated testing of qemu.git. Just let me know how I can do it. Cheers! Lucas