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 09:23:03 -0200 [thread overview]
Message-ID: <1297164183.2603.5.camel@freedom> (raw)
In-Reply-To: <AANLkTikcQ5mcXR+2GYg6r43=hBK4YTC5ZXpsrxqpFu6j@mail.gmail.com>
On Tue, 2011-02-08 at 09:23 +0000, Stefan Hajnoczi wrote:
> 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?
The biggest challenge is to have machines publicly accessible to perform
testing, right now we use the machines of our internal laboratory to
perform those tests. About notifiers of new git commits, I am unsure
whether we should test every and each git commit, since even sanity test
takes a while (the typical 84 tests of a sanity job take around 3 hours
to execute on fast machines). Of course, we might improve our ability to
perform parallel testing, or perhaps reducing test scope.
Bottom line, the thing here is to have available hardware externally
accessible, just like the buildbot that was setup, mentioned previously
on this thread.
next prev parent reply other threads:[~2011-02-08 11:23 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
2011-02-08 11:23 ` Lucas Meneghel Rodrigues [this message]
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=1297164183.2603.5.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).