qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.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, 8 Feb 2011 09:23:59 +0000	[thread overview]
Message-ID: <AANLkTikcQ5mcXR+2GYg6r43=hBK4YTC5ZXpsrxqpFu6j@mail.gmail.com> (raw)
In-Reply-To: <1297132183.2738.17.camel@freedom>

On Tue, Feb 8, 2011 at 2:29 AM, Lucas Meneghel Rodrigues <lmr@redhat.com> wrote:
> 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.

Yes, buildslaves are machines that execute builds and tests.  They
report the results back to the buildmaster which provides a public web
interface, breakage notifications, and central administration.

> 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.

Public automated qemu.git autotest would be excellent.  To be honest I
haven't had much visibility of KVM-Autotest myself as a QEMU/KVM
developer.  I suspect many others haven't either but there are big
benefits if we can change this.  By running your automated tests on
qemu.git in public we'll catch bugs earlier.

Do you want to add KVM-Autotest buildslave(s) or are you looking for
something like a HTTP POST notifier that pings you about new qemu.git
HEADs to test?

Stefan

  reply	other threads:[~2011-02-08  9:24 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
2011-02-08  9:23         ` Stefan Hajnoczi [this message]
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='AANLkTikcQ5mcXR+2GYg6r43=hBK4YTC5ZXpsrxqpFu6j@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=agraf@suse.de \
    --cc=andreas.faerber@web.de \
    --cc=gollub@b1-systems.de \
    --cc=lmr@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    /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).