From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [libvirt test] 65324: regressions - FAIL
Date: Fri, 04 Dec 2015 01:18:41 +0000 [thread overview]
Message-ID: <osstest-65324-mainreport@xen.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 5711 bytes --]
flight 65324 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65324/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR. vs. 63340
test-amd64-i386-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR. vs. 63340
test-amd64-amd64-libvirt-vhd 9 debian-di-install fail REGR. vs. 63340
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-raw 9 debian-di-install fail never pass
test-armhf-armhf-libvirt-qcow2 9 debian-di-install fail never pass
test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass
test-armhf-armhf-libvirt-xsm 14 guest-saverestore fail never pass
test-armhf-armhf-libvirt 14 guest-saverestore fail never pass
test-armhf-armhf-libvirt 12 migrate-support-check fail never pass
test-amd64-i386-libvirt 12 migrate-support-check fail never pass
test-amd64-i386-libvirt-xsm 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-xsm 12 migrate-support-check fail never pass
version targeted for testing:
libvirt d2e5538b16e325d9095f3ccb0dac88bbd9fc98f0
baseline version:
libvirt 3c7590e0a435d833895fc7b5be489e53e223ad95
Last test of basis 63340 2015-10-28 04:19:47 Z 36 days
Failing since 63352 2015-10-29 04:20:29 Z 35 days 31 attempts
Testing same since 65324 2015-12-03 04:21:16 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrea Bolognani <abologna@redhat.com>
Chen Hanxiao <chenhanxiao@gmail.com>
Christian Loehle <cloehle@linutronix.de>
Cole Robinson <crobinso@redhat.com>
Daniel P. Berrange <berrange@redhat.com>
Daniel Veillard <veillard@redhat.com>
Dmitry Andreev <dandreev@virtuozzo.com>
Erik Skultety <eskultet@redhat.com>
Guido Günther <agx@sigxcpu.org>
Ian Campbell <ian.campbell@citrix.com>
Jim Fehlig <jfehlig@suse.com>
Jiri Denemark <jdenemar@redhat.com>
Joao Martins <joao.m.martins@oracle.com>
John Ferlan <jferlan@redhat.com>
Ján Tomko <jtomko@redhat.com>
Laine Stump <laine@laine.org>
Luyao Huang <lhuang@redhat.com>
Marc-André Lureau <marcandre.lureau@gmail.com>
Martin Kletzander <mkletzan@redhat.com>
Maxim Perevedentsev <mperevedentsev@virtuozzo.com>
Michal Privoznik <mprivozn@redhat.com>
Michel Normand <normand@linux.vnet.ibm.com>
Mikhail Feoktistov <mfeoktistov@virtuozzo.com>
Nikolay Shirokovskiy <nshirokovskiy@virtuozzo.com>
Pavel Hrdina <phrdina@redhat.com>
Peter Krempa <pkrempa@redhat.com>
Richard Weinberger <richard@nod.at>
Roman Bogorodskiy <bogorodskiy@gmail.com>
Stefan Berger <stefanb@linux.vnet.ibm.com>
Stefan Berger <stefanb@us.ibm.com>
Wang Yufei <james.wangyufei@huawei.com>
Wei Jiangang <weijg.fnst@cn.fujitsu.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 pass
test-armhf-armhf-libvirt-xsm fail
test-amd64-i386-libvirt-xsm pass
test-amd64-amd64-libvirt pass
test-armhf-armhf-libvirt fail
test-amd64-i386-libvirt pass
test-amd64-amd64-libvirt-pair fail
test-amd64-i386-libvirt-pair fail
test-armhf-armhf-libvirt-qcow2 fail
test-armhf-armhf-libvirt-raw fail
test-amd64-amd64-libvirt-vhd fail
------------------------------------------------------------
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
Not pushing.
(No revision log; it would be 2870 lines long.)
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2015-12-04 1:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 1:18 osstest service owner [this message]
2015-12-04 9:54 ` [libvirt test] 65324: regressions - FAIL Joao Martins
2015-12-04 10:44 ` Ian Campbell
2015-12-04 10:38 ` Ian Campbell
2015-12-04 14:43 ` Stefano Stabellini
2015-12-04 15:00 ` Ian Campbell
2015-12-04 15:14 ` Stefano Stabellini
2015-12-04 15:22 ` Ian Campbell
2015-12-04 15:03 ` Ian Jackson
2015-12-07 1:14 ` Jim Fehlig
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-65324-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 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.