From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Glauber Costa <glommer@redhat.com>,
dlaor@redhat.com, Paul Brook <paul@codesourcery.com>,
qemu-devel@nongnu.org
Subject: Re: autotest (was Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT f80f9ec] Convert machine registration to use module initfunctions)
Date: Sun, 24 May 2009 23:50:54 +0300 [thread overview]
Message-ID: <4A19B32E.2020201@redhat.com> (raw)
In-Reply-To: <4A19A422.80807@us.ibm.com>
Anthony Liguori wrote:
> Autotest doesn't currently test the regressions that I want to test.
Which regressions do you want to test?
One way to increase coverage is to require each patch (fix or feature)
to come with a test. On the other hand, it might stop contributions
instead of increasing test coverage.
I've used this method for the x86 emulator in kvm, with some success.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-05-24 20:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200905211348.n4LDmnYd025976@d01av04.pok.ibm.com>
2009-05-21 22:36 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT f80f9ec] Convert machine registration to use module initfunctions Paul Brook
2009-05-21 22:50 ` Glauber Costa
2009-05-22 1:34 ` Anthony Liguori
2009-05-22 1:49 ` Glauber Costa
2009-05-22 2:00 ` Anthony Liguori
2009-05-23 14:22 ` autotest (was Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT f80f9ec] Convert machine registration to use module initfunctions) Dor Laor
2009-05-24 19:46 ` Anthony Liguori
2009-05-24 20:50 ` Avi Kivity [this message]
2009-05-26 8:10 ` Anthony Liguori
2009-05-26 9:17 ` Avi Kivity
2009-05-26 9:17 ` Dor Laor
2009-05-26 9:30 ` Anthony Liguori
2009-05-26 9:54 ` Dor Laor
2009-05-22 1:21 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT f80f9ec] Convert machine registration to use module initfunctions Anthony Liguori
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=4A19B32E.2020201@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=dlaor@redhat.com \
--cc=glommer@redhat.com \
--cc=paul@codesourcery.com \
--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).