From: Stefan Hajnoczi <stefanha@gmail.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] The state of testing
Date: Tue, 5 Mar 2013 11:45:09 +0100 [thread overview]
Message-ID: <20130305104509.GF1938@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <87ehfv9dlo.fsf@codemonkey.ws>
On Mon, Mar 04, 2013 at 01:20:03PM -0600, Anthony Liguori wrote:
> Stefan Hajnoczi <stefanha@gmail.com> writes:
>
> > People are working on testing for various parts of QEMU. I started
> > this thread to gather an update on the state of testing and see where
> > we still need help.
> >
> > I'm not sure yet if we should propose Google Summer of Code projects
> > to help with the testing infrastructure. Perhaps working on libqtest
> > support for PCI, USB, virtio, etc would be a cool project.
> >
> > Buildbot
> > ------------
> > The buildbot performs nightly builds and "make check". Test coverage
> > is still minimal but it's a starting point where we can add more tests
> > that will run every day.
> >
> > Block
> > --------
> > tests/qemu-iotests/ contains 49 tests for the block layer. These
> > tests mostly cover image format features like backing files,
> > snapshots, resize, and basic I/O verify tests.
> >
> > The test suite has a few areas for improvement:
> >
> > 1. aio is not well-supported. We need to be able to control the order
> > in which asynchronous requests complete in order to test all possible
> > code paths. This issue also means the current aio tests are not
> > deterministic and can fail randomly due to reordered output.
> >
> > 2. make check-block is not run by the buildbot. We should do so to
> > get nightly coverage of basic qcow2 tests. I will send a buildbot
> > config patch to fix this.
> >
> > Net
> > ---
> > No tests!
>
> qemu-test has a ping test that runs against rtl8139, e1000, virtio,
> ne2k_pci, i82551, i82557b, and i82559er.
>
> It also tests hotplug add/remove of network adapters with a variety of
> command line combinations.
>
> There's quite a few more things in qemu-test too.
Great, would it help to integrate qemu-test into the buildbot or do you
already have infrastructure to run it regularly on qemu.git/master?
Stefan
next prev parent reply other threads:[~2013-03-05 10:45 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
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 [this message]
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=20130305104509.GF1938@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@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).