From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [libvirt test] 103766: regressions - trouble: broken/fail/pass
Date: Tue, 20 Dec 2016 18:07:42 +0000 [thread overview]
Message-ID: <osstest-103766-mainreport@xen.org> (raw)
flight 103766 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103766/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-xsm 3 host-install(3) broken REGR. vs. 103479
test-amd64-i386-libvirt-xsm 3 host-install(3) broken REGR. vs. 103479
test-armhf-armhf-libvirt-qcow2 6 xen-boot fail REGR. vs. 103479
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt 13 saverestore-support-check fail like 103479
test-armhf-armhf-libvirt-raw 12 saverestore-support-check fail like 103479
test-armhf-armhf-libvirt-xsm 13 saverestore-support-check fail like 103479
Tests which did not succeed, but are not blocking:
test-amd64-i386-libvirt 12 migrate-support-check fail never pass
test-amd64-amd64-libvirt 12 migrate-support-check fail never pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass
test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass
test-armhf-armhf-libvirt 12 migrate-support-check fail never pass
test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass
test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass
version targeted for testing:
libvirt 9ab36bc233193acca290bb8eeb88b023bf45cdd0
baseline version:
libvirt 50b2a2375ad0eb26974039647fc705a32b10ac55
Last test of basis 103479 2016-12-16 17:26:38 Z 4 days
Testing same since 103766 2016-12-20 04:20:04 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Daniel P. Berrange <berrange@redhat.com>
Jiri Denemark <jdenemar@redhat.com>
Peter Krempa <pkrempa@redhat.com>
jobs:
build-amd64-xsm pass
build-armhf-xsm pass
build-i386-xsm pass
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-armhf-libvirt pass
build-i386-libvirt pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-libvirt-xsm broken
test-armhf-armhf-libvirt-xsm pass
test-amd64-i386-libvirt-xsm broken
test-amd64-amd64-libvirt pass
test-armhf-armhf-libvirt pass
test-amd64-i386-libvirt pass
test-amd64-amd64-libvirt-pair pass
test-amd64-i386-libvirt-pair pass
test-armhf-armhf-libvirt-qcow2 fail
test-armhf-armhf-libvirt-raw pass
test-amd64-amd64-libvirt-vhd pass
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
broken-step test-amd64-amd64-libvirt-xsm host-install(3)
broken-step test-amd64-i386-libvirt-xsm host-install(3)
Not pushing.
------------------------------------------------------------
commit 9ab36bc233193acca290bb8eeb88b023bf45cdd0
Author: Peter Krempa <pkrempa@redhat.com>
Date: Thu Dec 15 15:22:19 2016 +0100
locking: Fix documentation on how automatic sanlock leases are stored
s/MD5 checkout/MD5 hash/
commit 8551d39f4fbdb56551882ad3b48feb172da42ed6
Author: Peter Krempa <pkrempa@redhat.com>
Date: Thu Dec 15 15:09:47 2016 +0100
qemu: blockcopy: Save monitor error prior to calling into lock manager
The error would be overwritten otherwise producing a meaningless error
message.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1302171
commit 0dd1f7d2d7f4f0f23676bc1cd3bf34c60d2d9df2
Author: Daniel P. Berrange <berrange@redhat.com>
Date: Wed Dec 14 09:22:14 2016 +0000
docs: link to news file and other resources
In the website reorg we accidentally lost all links to the nice
reformatted news.html file. Add a link on the front page, and
also extend the download page table so that it includes links
to API docs and news files for each module (where available)
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
commit 5a26d1ce1249da99554946c37bce149c074c1022
Author: Daniel P. Berrange <berrange@redhat.com>
Date: Tue Dec 13 17:05:16 2016 +0000
Point to the new libvirt-go bindings
The github.com/rgbkrk/libvirt-go bindings were the most complete
bindings historically, but their API coverage stops at 1.2.4,
with exception of a couple of newer APIs.
The new bindings at http://libvirt.org/git/?p=libvirt-go.git;a=log
how have (almost[1]) 100% API coverage all the way to 2.5.0. They also
expose the APIs in a way that allows for much stronger go type
checking by the compiler, and expose typed parameters as explicit
structs. Finally the bindings are able to conditionally compile against
any libvirt version 1.2.0 -> 2.5.0 without use of go build tags.
Change the docs to point to these new bindings, since they'll be
a better bet for users long term.
[1] virEvent & virStream callbacks are still TODO to be fixed
real soon.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
commit 3d98acc9e36b3bce5745508cedd138b1a1683d97
Author: Jiri Denemark <jdenemar@redhat.com>
Date: Thu Dec 8 22:23:09 2016 +0100
network: Add support for local PTR domains
Similarly to localOnly DNS domain, localPtr attribute can be used to
tell the DNS server not to forward reverse lookups for unknown IPs which
belong to the virtual network.
Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
commit acd547dc9510224250a6237545f28e5b290f45f3
Author: Jiri Denemark <jdenemar@redhat.com>
Date: Thu Dec 8 22:21:39 2016 +0100
util: Introduce virSocketAddrPTRDomain
The API creates PTR domain which corresponds to a given addr/prefix.
Both IPv4 and IPv6 addresses are supported, but the prefix must be
divisible by 8 for IPv4 and divisible by 4 for IPv6.
The generated PTR domain has the following format
IPv4: 1.2.3.4.in-addr.arpa
IPv6: 0.1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.0.1.2.3.4.5.6.7.8.9.a.b.c.d.e.f.ip6.arpa
Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
commit 770b1d2b56d979202302a7dfd9ad38fd4825ac6c
Author: Jiri Denemark <jdenemar@redhat.com>
Date: Thu Dec 8 14:05:16 2016 +0100
conf: Make virNetworkIPDefParseXML a little bit saner
Iterating over all child nodes when we only support one instance of each
child is pretty weird. And it would even cause memory leaks if more
than one <tftp> element was specified.
Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
commit 9e9305542eee6700358c6f3c449347cc191eb520
Author: Peter Krempa <pkrempa@redhat.com>
Date: Fri Dec 16 18:30:39 2016 +0100
qemu: block copy: Forbid block copy to relative paths
Similarly to 29bb066915 forbid paths used with blockjobs to be relative.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1300177
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2016-12-20 18:07 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-103766-mainreport@xen.org \
--to=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).