From: Kevin Wolf <kwolf@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>, Qemu-devel@nongnu.org
Subject: [Qemu-devel] Merging qemu-iotests into qemu.git?
Date: Thu, 16 Feb 2012 16:01:58 +0100 [thread overview]
Message-ID: <4F3D1A66.8010909@redhat.com> (raw)
Hi Christoph,
I just talked to Stefan about our testing, both regarding the block
layer and qemu in general, and we came to the conclusion that it would
probably make sense to merge qemu-iotests into qemu.git.
The immediate benefit would be that we could include some short-running
tests into 'make check'. Long-term we would profit from being in the
same tests/ directory as all future tests for other qemu subsystems, so
we could probably share quite some of the framework code. (We were
initially talking about image streaming tests, which need a real VM
instead of just qemu-img/io and some monitor interaction - it's easy to
imagine similar cases)
What do you think?
Kevin
next reply other threads:[~2012-02-16 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 15:01 Kevin Wolf [this message]
2012-02-16 20:53 ` [Qemu-devel] Merging qemu-iotests into qemu.git? Christoph Hellwig
2012-02-20 16:42 ` Kevin Wolf
2012-02-22 14:34 ` 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=4F3D1A66.8010909@redhat.com \
--to=kwolf@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=hch@lst.de \
--cc=stefanha@linux.vnet.ibm.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).