From: Markus Armbruster <armbru@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH 1/1] tests/qtest: add scenario for -readconfig handling
Date: Tue, 09 Aug 2022 08:18:35 +0200 [thread overview]
Message-ID: <87h72mj5xg.fsf@pond.sub.org> (raw)
In-Reply-To: <YvFB/DZ+lYRHbd+U@redhat.com> ("Daniel P. Berrangé"'s message of "Mon, 8 Aug 2022 18:03:56 +0100")
Daniel P. Berrangé <berrange@redhat.com> writes:
> On Mon, Aug 08, 2022 at 07:55:50AM +0200, Thomas Huth wrote:
>> On 05/08/2022 13.55, Daniel P. Berrangé wrote:
>> > This test of -readconfig validates the last three regressions we
>> > have fixed with -readconfig:
>> >
>> > * Interpretation of memory size units as MiB not bytes
>> > * Allow use of [spice]
>> > * Allow use of [object]
>>
>> Good idea!
>>
>> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
[...]
>> > diff --git a/tests/qtest/readconfig-test.c b/tests/qtest/readconfig-test.c
>> > new file mode 100644
>> > index 0000000000..2e604d7c2d
>> > --- /dev/null
>> > +++ b/tests/qtest/readconfig-test.c
[...]
>> > +#ifdef CONFIG_SPICE
>> > +static void test_spice_resp(QObject *res)
>> > +{
>> > + Visitor *v;
>> > + g_autoptr(SpiceInfo) spice = NULL;
>> > +
>> > + g_assert(res);
>> > + v = qobject_input_visitor_new(res);
>> > + visit_type_SpiceInfo(v, "spcie", &spice, &error_abort);
>>
>> That "spcie" looks like a typo?
>
> Yes, but I believe this argument is ignored by the visitor in this
> scenario - it didn't fail for me at least.
include/qapi/visitor.h:
* The @name parameter of visit_type_FOO() describes the relation
* between this QAPI value and its parent container. When visiting
* the root of a tree, @name is ignored; when visiting a member of an
* object, @name is the key associated with the value; when visiting a
* member of a list, @name is NULL; and when visiting the member of an
* alternate, @name should equal the name used for visiting the
* alternate.
> Regardless, sHould be fixed of course
>
>
> With regards,
> Daniel
prev parent reply other threads:[~2022-08-09 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 11:55 [PATCH 0/1] tests/qtest: add testing coverage of -readconfig Daniel P. Berrangé
2022-08-05 11:55 ` [PATCH 1/1] tests/qtest: add scenario for -readconfig handling Daniel P. Berrangé
2022-08-08 5:55 ` Thomas Huth
2022-08-08 17:03 ` Daniel P. Berrangé
2022-08-09 6:18 ` Markus Armbruster [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=87h72mj5xg.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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.