From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: afaerber@suse.de, stefanha@redhat.com, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 4/7] device-introspect-test: New, covering device introspection
Date: Fri, 25 Sep 2015 12:17:33 +0200 [thread overview]
Message-ID: <56051F3D.70900@redhat.com> (raw)
In-Reply-To: <1443121042-3409-5-git-send-email-armbru@redhat.com>
On 24/09/15 20:57, Markus Armbruster wrote:
> The test doesn't check that the output makes any sense, only that QEMU
> survives. Useful since we've had an astounding number of crash bugs
> around there.
>
> In fact, we have a bunch of them right now: several devices crash or
> hang, and all CPUs leave a dangling pointer behind. The test skips
> testing the broken parts. The next commits will fix them, and drop
> the skipping.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> ---
> tests/Makefile | 8 ++-
> tests/device-introspect-test.c | 153 +++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 158 insertions(+), 3 deletions(-)
> create mode 100644 tests/device-introspect-test.c
Hi Markus,
just a quick note: When I run the tester directly, it aborts:
$ tests/boot-order-test
**
ERROR:/home/thuth/devel/qemu/tests/libqtest.c:517:qtest_get_arch:
assertion failed: (qemu != NULL)
Aborted (core dumped)
... that's a little bit ugly, maybe you could print the help text instead?
Thomas
next prev parent reply other threads:[~2015-09-25 10:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 18:57 [Qemu-devel] [PATCH v3 0/7] Fix device introspection regressions Markus Armbruster
2015-09-24 18:57 ` [Qemu-devel] [PATCH v3 1/7] tests: Fix how qom-test is run Markus Armbruster
2015-09-24 18:57 ` [Qemu-devel] [PATCH v3 2/7] libqtest: Clean up unused QTestState member sigact_old Markus Armbruster
2015-09-24 18:57 ` [Qemu-devel] [PATCH v3 3/7] libqtest: New hmp() & friends Markus Armbruster
2015-09-24 18:57 ` [Qemu-devel] [PATCH v3 4/7] device-introspect-test: New, covering device introspection Markus Armbruster
2015-09-25 10:17 ` Thomas Huth [this message]
2015-09-25 10:18 ` Andreas Färber
2015-09-25 14:13 ` Markus Armbruster
2015-09-24 18:57 ` [Qemu-devel] [PATCH v3 5/7] qmp: Fix device-list-properties not to crash for abstract device Markus Armbruster
2015-09-24 18:57 ` [Qemu-devel] [PATCH v3 6/7] qdev: Protect device-list-properties against broken devices Markus Armbruster
2015-09-24 19:25 ` Eduardo Habkost
2015-09-25 6:07 ` Markus Armbruster
2015-09-25 13:38 ` Thomas Huth
2015-09-25 14:17 ` Markus Armbruster
2015-09-25 18:21 ` Thomas Huth
2015-09-28 8:11 ` Markus Armbruster
2015-09-28 8:15 ` Andreas Färber
2015-09-28 8:38 ` Paolo Bonzini
2015-09-28 8:37 ` Paolo Bonzini
2015-09-28 14:17 ` Markus Armbruster
2015-09-28 14:25 ` Paolo Bonzini
2015-09-28 9:17 ` Thomas Huth
2015-09-28 9:30 ` Peter Maydell
2015-09-28 14:35 ` Markus Armbruster
2015-09-28 14:44 ` Peter Maydell
2015-09-28 19:36 ` Markus Armbruster
2015-09-28 19:40 ` Peter Maydell
2015-09-29 8:05 ` Markus Armbruster
2015-09-29 12:38 ` Paolo Bonzini
2015-09-24 18:57 ` [Qemu-devel] [PATCH v3 7/7] Revert "qdev: Use qdev_get_device_class() for -device <type>, help" Markus Armbruster
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=56051F3D.70900@redhat.com \
--to=thuth@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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.