From: Jim Fehlig <jfehlig@suse.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: libvir-list@redhat.com, xen-devel@lists.xensource.com,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH 5/5] Add a test suite for libxl option generator
Date: Mon, 02 Jun 2014 15:42:36 -0600 [thread overview]
Message-ID: <538CEFCC.1040108@suse.com> (raw)
In-Reply-To: <20140602125752.GI28039@redhat.com>
Daniel P. Berrange wrote:
> On Mon, Jun 02, 2014 at 01:53:46PM +0100, Ian Campbell wrote:
>
>> On Fri, 2014-05-30 at 18:24 +0100, Daniel P. Berrange wrote:
>>
>>> + if (STRNEQ(expectargv, (char *)actualargv)) {
>>> + virtTestDifference(stderr, expectargv, (char *)actualargv);
>>> + goto cleanup;
>>> + }
>>>
>> Since you are using libxl_domain_config_gen_json you can control the
>> pretty printing, but if you were to use the libxl_domain_config_to_json
>> you might have problems if the library was to do something slightly
>> different e.g. with whitespace.
>>
>> In 4.5 we will have libxl_*_from_json and (I think) libxl_*_compare, so
>> you could read in the template and compare it with the generated struct.
>> That doesn't help you now of course.
>>
>> Also in 4.5 the json will omit fields which are set to the their
>> explicit default value. libxl_*_from_json will still do the right thing,
>> but it'd be another annoyance for you here I think.
>>
>> Lastly, when we add new fields to the API they will start showing up in
>> the json (modulo the omission of defaults discussed above).
>>
>
> Hmm, that's a v good point.
>
One that can already be seen. The test works when run on Xen 4.3, but
fails on 4.4. E.g. c_info gained some new fields
"poolid": 0,
"run_hotplug_scripts": "<default>",
+ "pvh": "<default>",
+ "driver_domain": "<default>"
},
And on_watchdog's value changed
"on_poweroff": null,
"on_reboot": "destroy",
- "on_watchdog": null,
+ "on_watchdog": "destroy",
"on_crash": "destroy"
Regards,
Jim
next prev parent reply other threads:[~2014-06-02 21:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 17:24 [libvirt] [PATCH 0/5] Testing libvirt XML -> libxl_domain_config conversion Daniel P. Berrange
2014-05-30 17:24 ` [libvirt] [PATCH 1/5] Don't pass virDomainObjPtr to libxlBuildDomainConfig Daniel P. Berrange
2014-05-30 22:26 ` Jim Fehlig
2014-05-30 17:24 ` [libvirt] [PATCH 2/5] Don't pass libxlDriverPrivatePtr into libxlBuildDomainConfig Daniel P. Berrange
2014-05-30 22:34 ` Jim Fehlig
2014-05-30 17:24 ` [libvirt] [PATCH 3/5] libxl: Move virDomainXMLOptionNew into libxlCreateXMLConf Daniel P. Berrange
2014-05-30 22:41 ` Jim Fehlig
2014-06-02 9:33 ` Daniel P. Berrange
2014-05-30 17:24 ` [libvirt] [PATCH 4/5] Add more test suite mock helpers Daniel P. Berrange
2014-05-30 17:24 ` [PATCH 5/5] Add a test suite for libxl option generator Daniel P. Berrange
2014-06-02 12:53 ` Ian Campbell
2014-06-02 12:57 ` [libvirt] [Xen-devel] " Daniel P. Berrange
2014-06-02 21:42 ` Jim Fehlig [this message]
2014-06-02 12:41 ` [PATCH 0/5] Testing libvirt XML -> libxl_domain_config conversion Ian Campbell
2014-06-02 12:49 ` [libvirt] [Xen-devel] " Daniel P. Berrange
2014-06-02 22:43 ` Jim Fehlig
2014-06-03 9:26 ` [libvirt] [Xen-devel] " Daniel P. Berrange
2014-06-02 12:57 ` Ian Campbell
2014-06-02 13:15 ` Processed: " xen
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=538CEFCC.1040108@suse.com \
--to=jfehlig@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=berrange@redhat.com \
--cc=libvir-list@redhat.com \
--cc=xen-devel@lists.xensource.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).