qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.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>,
	qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] The state of testing
Date: Mon, 11 Mar 2013 14:22:36 +0530	[thread overview]
Message-ID: <20130311085236.GA979@amit.redhat.com> (raw)
In-Reply-To: <5136151E.5050206@redhat.com>

On (Tue) 05 Mar 2013 [12:54:06], Lucas Meneghel Rodrigues wrote:
> On 03/05/2013 07:11 AM, Amit Shah wrote:
> >On (Mon) 04 Mar 2013 [16:53:55], Stefan Hajnoczi wrote:

> >>How are things looking with device emulation, migration, monitor, char, etc?
> >
> >I have a few tests coded up for virtio-serial at
> >
> >http://fedorapeople.org/cgit/amitshah/public_git/test-virtserial.git/
> >
> >which indirectly test chardevs.
> >
> >Autotest (virt-tests) also has virtio-serial tests which end up
> >testing chardevs.
> 
> >chardevs, being an external interface to qemu, do get tested whenever
> >anyone starts qemu with e.g. libvirt.
> >
> >Also, autotest has libvirt-based tests, which exercise the monitor.
> >However, I don't think there's anything comprehensive anywhere.
> 
> The virtio console tests span over 130 tests, and take ~4 hours to
> run, I'd consider they are comprehensive.

It's a commendable job the folks who've put together the tests have
done.

However, it's still not comprehensive for the chardevs themselves.
For example, guest freezes for lack of flow control would've been
flagged by autotest otherwise.  Though I'm happy to now note that will
no longer be an issue on qemu.git, and we must now add tests for
checking flow control.

		Amit

      reply	other threads:[~2013-03-11  8:52 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
2013-03-05 10:11 ` Amit Shah
2013-03-05 15:54   ` Lucas Meneghel Rodrigues
2013-03-11  8:52     ` Amit Shah [this message]

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=20130311085236.GA979@amit.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@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 \
    --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 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).