From: Anthony Liguori <aliguori@us.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Cc: Amit Shah <amit.shah@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Markus Armbruster <armbru@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] The state of testing
Date: Mon, 04 Mar 2013 13:20:03 -0600 [thread overview]
Message-ID: <87ehfv9dlo.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAJSP0QU=bK86EBN3o2_92kve2sGVj2eo6-iN2cYKatLz9gnZHQ@mail.gmail.com>
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.
Regards,
Anthony Liguori
>
> How are things looking with device emulation, migration, monitor, char, etc?
>
> Stefan
next prev parent reply other threads:[~2013-03-04 19:20 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 [this message]
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=87ehfv9dlo.fsf@codemonkey.ws \
--to=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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.