All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.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, 05 Mar 2013 12:17:23 +0100	[thread overview]
Message-ID: <5135D443.2070208@redhat.com> (raw)
In-Reply-To: <20130305104605.GG1938@stefanha-thinkpad.redhat.com>

On 03/05/13 11:46, Stefan Hajnoczi wrote:
> On Mon, Mar 04, 2013 at 05:22:34PM +0100, Gerd Hoffmann wrote:
>>   Hi,
>>
>>> How are things looking with device emulation, migration, monitor, char, etc?
>>
>> At the moment autotest/virt-test is pretty much the only workable thing
>> for non-trivial devices because libqtest lacks infrastructure for pci
>> and anything building on top of pci.
>>
>> usb has no in-tree tests, but has autotest coverage.
>>
>> chardevs have some autotest coverage, /me wrote a test for
>> chardev-{add,remove} qmp commands.  Still need to rebase + polish +
>> submit that one though.
> 
> Do the USB and chardev tests run regularly against qemu.git/master?

I don't think we have *any* regular autotest coverage for master, have we?

I run the usb tests locally now and then.

The chardev test was used as development aid, as mentioned I still have
to get it upstream so it can be used for regression testing.

cheers,
  Gerd

  reply	other threads:[~2013-03-05 11:17 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 [this message]
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

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=5135D443.2070208@redhat.com \
    --to=kraxel@redhat.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 \
    --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.