From: xen.org <Ian.Jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [libvirt test] 29597: regressions - FAIL
Date: Mon, 4 Aug 2014 21:20:44 +0100 [thread overview]
Message-ID: <osstest-29597-mainreport@xen.org> (raw)
flight 29597 libvirt real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/29597/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf 5 xen-build fail REGR. vs. 29585
Tests which did not succeed, but are not blocking:
test-amd64-i386-libvirt 9 guest-start fail never pass
test-armhf-armhf-libvirt 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt 9 guest-start fail never pass
build-armhf-libvirt 1 build-check(1) blocked n/a
version targeted for testing:
libvirt 21b59b651c6ef97a3cead20211c01d71d4e32c45
baseline version:
libvirt be3cbecd0ef0c5b2d711d1451261cd8ad4e0228e
------------------------------------------------------------
People who touched revisions under test:
Daniel Veillard <veillard@redhat.com>
Eric Blake <eblake@redhat.com>
Laine Stump <laine@laine.org>
------------------------------------------------------------
jobs:
build-amd64 pass
build-armhf fail
build-i386 pass
build-amd64-libvirt pass
build-armhf-libvirt blocked
build-i386-libvirt pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
test-amd64-amd64-libvirt fail
test-armhf-armhf-libvirt blocked
test-amd64-i386-libvirt fail
------------------------------------------------------------
sg-report-flight on osstest.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images
Logs, config files, etc. are available at
http://www.chiark.greenend.org.uk/~xensrcts/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Not pushing.
------------------------------------------------------------
commit 21b59b651c6ef97a3cead20211c01d71d4e32c45
Author: Daniel Veillard <veillard@redhat.com>
Date: Sun Aug 3 08:55:15 2014 -0400
Release of libvirt-1.2.7
* docs/news.html.in libvirt.spec.in: update for the release
* po/*.po*: update localizations and regenerate
commit 478d93ad1f83084bb0277fec07e1ef441a09018f
Author: Eric Blake <eblake@redhat.com>
Date: Sat Aug 2 20:47:36 2014 -0600
build: fix build on cygwin
Cygwin has getifaddrs(), but not AF_LINK, leading to:
util/virstats.c: In function 'virNetInterfaceStats':
util/virstats.c:138:41: error: 'AF_LINK' undeclared (first use in this function)
if (ifa->ifa_addr->sa_family != AF_LINK)
...
* src/util/virstats.c (virNetInterfaceStats): Only use getifaddrs
if AF_LINK is present.
Signed-off-by: Eric Blake <eblake@redhat.com>
commit c0788af07d08f0e2297736764766d78ff72ae034
Author: Laine Stump <laine@laine.org>
Date: Fri Aug 1 17:51:37 2014 -0400
network: always set disable_ipv6, even when it should be 0
libvirt previously only touched an interface's disable_ipv6 setting in
sysfs if it needed to be set to 1, assuming that 0 is the
default. Apparently that isn't always the case though (kernel 3.15.7-1
in Arch Linux reportedly defaults a new interface's disable_ipv6
setting to 1) so this patch explicitly sets it to 0 or 1 as
appropriate.
reply other threads:[~2014-08-04 20:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=osstest-29597-mainreport@xen.org \
--to=ian.jackson@eu.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 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).