qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Michael Tokarev" <mjt@tls.msk.ru>,
	"Alexander Graf" <agraf@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Andreas Färber" <andreas.faerber@web.de>,
	gollub@b1-systems.de
Subject: [Qemu-devel] Re: Buildbot for qemu.git/master
Date: Tue, 08 Feb 2011 00:29:43 -0200	[thread overview]
Message-ID: <1297132183.2738.17.camel@freedom> (raw)
In-Reply-To: <AANLkTikHds498i=HXfbhwLmoy1FxSpAi-gnC7VUfPqCT@mail.gmail.com>

On Mon, 2011-02-07 at 14:36 +0000, Stefan Hajnoczi wrote:
> On Mon, Feb 7, 2011 at 1:00 PM, Alexander Graf <agraf@suse.de> 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

  parent reply	other threads:[~2011-02-08  2:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05 16:36 [Qemu-devel] Buildbot for qemu.git/master Stefan Hajnoczi
2011-02-05 20:32 ` [Qemu-devel] " Stefan Hajnoczi
2011-02-07 13:00   ` Alexander Graf
2011-02-07 14:36     ` Stefan Hajnoczi
2011-02-07 14:44       ` Alexander Graf
2011-02-07 15:26         ` Stefan Hajnoczi
2011-02-08  2:29       ` Lucas Meneghel Rodrigues [this message]
2011-02-08  9:23         ` Stefan Hajnoczi
2011-02-08 11:23           ` Lucas Meneghel Rodrigues
2011-02-08 11:26             ` Alexander Graf
2011-02-08 11:28             ` Stefan Hajnoczi
2011-02-08 12:32               ` Alexander Graf
2011-02-07 19:03   ` Luiz Capitulino
2011-02-07 21:18     ` Stefan Hajnoczi
2011-02-07 21:23       ` Alexander Graf
2011-02-07  8:30 ` Daniel Gollub
2011-02-07  9:34   ` Stefan Hajnoczi
2011-02-08 11:14     ` Daniel Gollub
2011-02-08 11:39       ` Stefan Hajnoczi
2011-02-07 15:02 ` [Qemu-devel] " Richard W.M. Jones
2011-02-07 15:15   ` Stefan Hajnoczi
2011-02-08  2:36     ` Lucas Meneghel Rodrigues

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=1297132183.2738.17.camel@freedom \
    --to=lmr@redhat.com \
    --cc=agraf@suse.de \
    --cc=andreas.faerber@web.de \
    --cc=gollub@b1-systems.de \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).