From: Cedric Bosdonnat <cbosdonnat@suse.com>
To: Wei Liu <wei.liu2@citrix.com>,
osstest service owner <osstest-admin@xenproject.org>,
Jim Fehlig <jfehlig@suse.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-unstable-smoke test] 103306: regressions - FAIL
Date: Wed, 14 Dec 2016 09:26:36 +0100 [thread overview]
Message-ID: <1481703996.2789.1.camel@suse.com> (raw)
In-Reply-To: <20161214075237.GA16913@citrix.com>
Hello Wei,
On Wed, 2016-12-14 at 07:52 +0000, Wei Liu wrote:
> On Wed, Dec 14, 2016 at 06:24:15AM +0000, osstest service owner wrote:
> > flight 103306 xen-unstable-smoke real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/103306/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > build-amd64-libvirt 5 libvirt-build fail REGR. vs. 103284
> >
>
> xenconfig/xen_xl.c: In function 'xenParseXLDisk':
> xenconfig/xen_xl.c:376:17: error: enumeration value 'LIBXL_DISK_FORMAT_QED' not handled in switch [-Werror=switch]
> switch (libxldisk->format) {
> ^
> cc1: all warnings being treated as errors
>
> It seems that libvirt is not happy with the recent addition of new disk
> format in xen.git:
>
> 1035fe9b160bf298985296a6c73f2ab3d1ae55c5 libxl: QED disks support
>
> The short term fix is, of course, to add the corresponding format to
> libvirt. But I'm not sure what the long term fix is.
I have a pending libvirt patch add QED support here that I'll need to
rewrite and submit now that the libxl one is nearly pushed.
--
Cedric
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-12-14 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 6:24 [xen-unstable-smoke test] 103306: regressions - FAIL osstest service owner
2016-12-14 7:52 ` Wei Liu
2016-12-14 8:26 ` Cedric Bosdonnat [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=1481703996.2789.1.camel@suse.com \
--to=cbosdonnat@suse.com \
--cc=jfehlig@suse.com \
--cc=osstest-admin@xenproject.org \
--cc=wei.liu2@citrix.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 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.