From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, mdroth@linux.vnet.ibm.com, aliguori@amazon.com
Subject: [Qemu-devel] [PATCH 00/10] qapi: Test coverage & clean up generated code
Date: Thu, 6 Feb 2014 15:29:50 +0100 [thread overview]
Message-ID: <1391697000-5855-1-git-send-email-armbru@redhat.com> (raw)
Coverity is unhappy with the generated code. Nothing serious, just
heaps of valid DEADCODE defects topped off with a few bogus
FORWARD_NULL defects.
I had a look at the generator, and decided I don't want to mess with
it without decent test coverage. Unfortunately, a few features have
been added without tests. My first seven patches make the tests catch
up. tests/qapi-schema/qapi-schema-test.json now covers all mcgen() in
scripts/qapi*.py, except for a few in qapi-commands.py that are
conditional on -m.
My last three patches clean up the generated code.
Markus Armbruster (10):
tests/qapi-schema: Actually check successful QMP command response
tests/qapi-schema: Cover optional command arguments
tests/qapi-schema: Cover simple argument types
tests/qapi-schema: Cover anonymous union types
tests/qapi-schema: Cover complex types with base
tests/qapi-schema: Cover union types with base
tests/qapi-schema: Cover flat union types
qapi: Drop nonsensical header guard in generated qapi-visit.c
qapi: Drop unused code in qapi-commands.py
qapi: Clean up null checking in generated visitors
scripts/qapi-commands.py | 20 ---------
scripts/qapi-visit.py | 16 +++----
tests/qapi-schema/qapi-schema-test.json | 24 +++++++++-
tests/qapi-schema/qapi-schema-test.out | 19 +++++---
tests/test-qmp-commands.c | 79 +++++++++++++++++++++++++++------
tests/test-qmp-input-strict.c | 69 +++++++++++++++++++++++++++-
tests/test-qmp-input-visitor.c | 45 +++++++++++++++++--
tests/test-qmp-output-visitor.c | 67 ++++++++++++++++++++++++++--
tests/test-visitor-serialization.c | 14 +++---
9 files changed, 288 insertions(+), 65 deletions(-)
--
1.8.1.4
next reply other threads:[~2014-02-06 14:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 14:29 Markus Armbruster [this message]
2014-02-06 14:29 ` [Qemu-devel] [PATCH 01/10] tests/qapi-schema: Actually check successful QMP command response Markus Armbruster
2014-02-07 2:09 ` Eric Blake
2014-02-07 7:37 ` Markus Armbruster
2014-02-06 14:29 ` [Qemu-devel] [PATCH 02/10] tests/qapi-schema: Cover optional command arguments Markus Armbruster
2014-02-07 2:30 ` Eric Blake
2014-02-06 14:29 ` [Qemu-devel] [PATCH 03/10] tests/qapi-schema: Cover simple argument types Markus Armbruster
2014-02-07 2:32 ` Eric Blake
2014-02-06 14:29 ` [Qemu-devel] [PATCH 04/10] tests/qapi-schema: Cover anonymous union types Markus Armbruster
2014-02-07 2:35 ` Eric Blake
2014-02-06 14:29 ` [Qemu-devel] [PATCH 05/10] tests/qapi-schema: Cover complex types with base Markus Armbruster
2014-02-07 2:38 ` Eric Blake
2014-02-06 14:29 ` [Qemu-devel] [PATCH 06/10] tests/qapi-schema: Cover union " Markus Armbruster
2014-02-07 2:40 ` Eric Blake
2014-02-06 14:29 ` [Qemu-devel] [PATCH 07/10] tests/qapi-schema: Cover flat union types Markus Armbruster
2014-02-07 2:51 ` Eric Blake
2014-02-06 14:29 ` [Qemu-devel] [PATCH 08/10] qapi: Drop nonsensical header guard in generated qapi-visit.c Markus Armbruster
2014-02-07 2:52 ` Eric Blake
2014-02-06 14:29 ` [Qemu-devel] [PATCH 09/10] qapi: Drop unused code in qapi-commands.py Markus Armbruster
2014-02-07 2:56 ` Eric Blake
2014-02-06 14:30 ` [Qemu-devel] [PATCH 10/10] qapi: Clean up null checking in generated visitors Markus Armbruster
2014-02-07 3:10 ` Eric Blake
2014-02-07 7:34 ` Markus Armbruster
2014-02-07 12:42 ` Paolo Bonzini
2014-02-07 14:23 ` Markus Armbruster
2014-02-07 14:45 ` Paolo Bonzini
2014-02-10 13:29 ` Markus Armbruster
2014-02-11 9:06 ` Paolo Bonzini
2014-02-11 12:35 ` 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=1391697000-5855-1-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=aliguori@amazon.com \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
/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).