From: Jim Fehlig <jfehlig@suse.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Subject: Re: [libvirt test] 91597: regressions - FAIL
Date: Mon, 18 Apr 2016 11:04:39 -0600 [thread overview]
Message-ID: <571513A7.70506@suse.com> (raw)
In-Reply-To: <osstest-91597-mainreport@xen.org>
On 04/16/2016 05:54 AM, osstest service owner wrote:
> flight 91597 libvirt real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/91597/
>
> 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. 91479
> build-i386-libvirt 5 libvirt-build fail REGR. vs. 91479
> build-armhf-libvirt 5 libvirt-build fail REGR. vs. 91479
These build failures (warnings treated as errors) surfaced after defining
LIBXL_API_VERSION=0x040200. E.g.
In file included from
/home/osstest/build.91597.build-amd64-libvirt/xendist/usr/local/include/libxl.h:439:0,
from libxl/libxl_domain.h:27,
from libxl/libxl_domain.c:28:
/home/osstest/build.91597.build-amd64-libvirt/xendist/usr/local/include/libxl_uuid.h:64:1:
error: 'static' is not at beginning of declaration [-Werror=old-style-declaration]
void static inline libxl_uuid_copy_0x040400(libxl_uuid *dst,
^
/home/osstest/build.91597.build-amd64-libvirt/xendist/usr/local/include/libxl_uuid.h:64:1:
error: 'inline' is not at beginning of declaration [-Werror=old-style-declaration]
I suppose the obvious fix is to change the declarations and backport to all
maintained releases. Another option is suppressing the warning. Or perhaps a
better trick?
Regards,
Jim
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-18 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 11:54 [libvirt test] 91597: regressions - FAIL osstest service owner
2016-04-18 17:04 ` Jim Fehlig [this message]
2016-04-20 13:31 ` Wei Liu
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=571513A7.70506@suse.com \
--to=jfehlig@suse.com \
--cc=osstest-admin@xenproject.org \
--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).