From: Stefan Hajnoczi <stefanha@gmail.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Juan Quintela <quintela@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>,
Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] The state of testing
Date: Wed, 6 Mar 2013 10:53:08 +0100 [thread overview]
Message-ID: <20130306095308.GA1954@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <51361B7E.2030709@redhat.com>
On Tue, Mar 05, 2013 at 01:21:18PM -0300, Lucas Meneghel Rodrigues wrote:
> On 03/05/2013 01:14 PM, Gerd Hoffmann wrote:
> > Hi,
> >
> >>>I don't think we have *any* regular autotest coverage for master, have
> >>>we?
> >>
> >>^ Yes, there is coverage. There's a daily job called sanity that takes
> >>about 2.5 hours, that builds the latest kvm.git and installs it in the
> >>host, then reboots the box, builds the latest qemu master and runs:
> >
> >Oh, good. I guess it would be a good idea to send reports to
> >qemu-devel, maybe a weekly status or mails on regressions simliar to the
> >buildbot build failures. So people (a) aware that the service exists in
> >the first place and (b) get informed that something broke which should
> >be fixed.
>
> No doubt, I did try that before, but from my experience, the reports
> are likely to be ignored and people will complain about SPAM.
>
> So we ended up creating an internal mailing list where Gleb and
> Marcelo are subscribed to, in case they want to look at the reports,
> and I'd look at the reports and report on the ML in case something
> bad happens.
I understand that SPAM issue. Maybe only send failures to the list?
The reason why it's important to include qemu-devel@nongnu.org is that
in the current mode you are essentially just reporting bugs. This is
different from providing maintainers test results and failure
notifications so the tests become part of the QEMU development and
release process.
That's an important distinction. Maintainers need to see the test
status (e.g. "99/102 tests passing") and have the ability to dig deeper
- especially during the hard freeze period where we shake out bugs. If
maintainers have no visibility then the tests are not part of the
development process.
The way that buildbot does this is and I think the same is possible for
kvm autotest:
1. Send failure notifications to qemu-devel.
2. Provide a website to check the status
http://buildbot.b1-systems.de/qemu/.
If you want help, please let me know. qemu.org could host
web-accessible test results. We can check with Anthony and I can help
you set it up.
Stefan
next prev parent reply other threads:[~2013-03-06 9:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 15:53 [Qemu-devel] The state of testing Stefan Hajnoczi
2013-03-04 16:22 ` Gerd Hoffmann
2013-03-04 17:26 ` mdroth
2013-03-05 9:46 ` Kevin Wolf
2013-03-05 10:46 ` Stefan Hajnoczi
2013-03-05 11:17 ` Gerd Hoffmann
2013-03-05 15:59 ` Lucas Meneghel Rodrigues
2013-03-05 16:14 ` Gerd Hoffmann
2013-03-05 16:21 ` Lucas Meneghel Rodrigues
2013-03-06 9:53 ` Stefan Hajnoczi [this message]
2013-03-06 12:00 ` Markus Armbruster
2013-03-05 16:09 ` Lucas Meneghel Rodrigues
2013-03-05 16:23 ` Gerd Hoffmann
2013-03-05 16:41 ` Lucas Meneghel Rodrigues
2013-03-04 19:20 ` Anthony Liguori
2013-03-05 10:45 ` Stefan Hajnoczi
2013-03-05 10:11 ` Amit Shah
2013-03-05 15:54 ` Lucas Meneghel Rodrigues
2013-03-11 8:52 ` Amit Shah
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=20130306095308.GA1954@stefanha-thinkpad.muc.redhat.com \
--to=stefanha@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=lmr@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).