From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [libvirt test] 149773: regressions - FAIL
Date: Fri, 24 Apr 2020 09:53:03 +0000 [thread overview]
Message-ID: <osstest-149773-mainreport@xen.org> (raw)
flight 149773 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/149773/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-build fail REGR. vs. 146182
build-i386-libvirt 6 libvirt-build fail REGR. vs. 146182
build-arm64-libvirt 6 libvirt-build fail REGR. vs. 146182
build-armhf-libvirt 6 libvirt-build fail REGR. vs. 146182
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt-xsm 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a
test-amd64-i386-libvirt 1 build-check(1) blocked n/a
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a
test-amd64-i386-libvirt-xsm 1 build-check(1) blocked n/a
test-arm64-arm64-libvirt-xsm 1 build-check(1) blocked n/a
test-armhf-armhf-libvirt-raw 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt-vhd 1 build-check(1) blocked n/a
test-arm64-arm64-libvirt 1 build-check(1) blocked n/a
test-amd64-i386-libvirt-pair 1 build-check(1) blocked n/a
test-arm64-arm64-libvirt-qcow2 1 build-check(1) blocked n/a
test-armhf-armhf-libvirt 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt-pair 1 build-check(1) blocked n/a
version targeted for testing:
libvirt e2f1e2687fe5c976d1aecbae9350e761f1d1ddc0
baseline version:
libvirt a1cd25b919509be2645dbe6f952d5263e0d4e4e5
Last test of basis 146182 2020-01-17 06:00:23 Z 98 days
Failing since 146211 2020-01-18 04:18:52 Z 97 days 90 attempts
Testing same since 149773 2020-04-24 04:18:45 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrea Bolognani <abologna@redhat.com>
Arnaud Patard <apatard@hupstream.com>
Bjoern Walk <bwalk@linux.ibm.com>
Boris Fiuczynski <fiuczy@linux.ibm.com>
Chen Hanxiao <chen_han_xiao@126.com>
Christian Borntraeger <borntraeger@de.ibm.com>
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Christian Schoenebeck <qemu_oss@crudebyte.com>
Collin Walling <walling@linux.ibm.com>
Cornelia Huck <cohuck@redhat.com>
Daniel Henrique Barboza <danielhb413@gmail.com>
Daniel P. Berrangé <berrange@redhat.com>
Daniel Veillard <veillard@redhat.com>
Dario Faggioli <dfaggioli@suse.com>
Erik Skultety <eskultet@redhat.com>
Gaurav Agrawal <agrawalgaurav@gnome.org>
Han Han <hhan@redhat.com>
Jamie Strandboge <jamie@canonical.com>
Jim Fehlig <jfehlig@suse.com>
Jiri Denemark <jdenemar@redhat.com>
Jonathon Jongsma <jjongsma@redhat.com>
Julio Faracco <jcfaracco@gmail.com>
Ján Tomko <jtomko@redhat.com>
Laine Stump <laine@redhat.com>
Leonid Bloch <lb.workbox@gmail.com>
Lin Ma <LMa@suse.com>
Marc-André Lureau <marcandre.lureau@redhat.com>
Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Mark Asselstine <mark.asselstine@windriver.com>
Mauro S. M. Rodrigues <maurosr@linux.vnet.ibm.com>
Michal Privoznik <mprivozn@redhat.com>
Nikolay Shirokovskiy <nshirokovskiy@virtuozzo.com>
Pavel Hrdina <phrdina@redhat.com>
Pavel Mores <pmores@redhat.com>
Peter Krempa <pkrempa@redhat.com>
Philipp Hahn <hahn@univention.de>
Pino Toscano <ptoscano@redhat.com>
Prathamesh Chavan <pc44800@gmail.com>
Rafael Fonseca <r4f4rfs@gmail.com>
Richard W.M. Jones <rjones@redhat.com>
Rikard Falkeborn <rikard.falkeborn@gmail.com>
Ryan Moeller <ryan@iXsystems.com>
Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com>
Sebastian Mitterle <smitterl@redhat.com>
Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>
Stefan Berger <stefanb@linux.ibm.com>
Stefan Berger <stefanb@linux.vnet.ibm.com>
Stefan Hajnoczi <stefanha@redhat.com>
Thomas Huth <thuth@redhat.com>
Wu Qingliang <wuqingliang4@huawei.com>
Yi Li <yili@winhong.com>
Your Name <you@example.com>
Zhang Bo <oscar.zhangbo@huawei.com>
zhenwei pi <pizhenwei@bytedance.com>
Zhimin Feng <fengzhimin1@huawei.com>
jobs:
build-amd64-xsm pass
build-arm64-xsm pass
build-i386-xsm pass
build-amd64 pass
build-arm64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt fail
build-arm64-libvirt fail
build-armhf-libvirt fail
build-i386-libvirt fail
build-amd64-pvops pass
build-arm64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm blocked
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm blocked
test-amd64-amd64-libvirt-xsm blocked
test-arm64-arm64-libvirt-xsm blocked
test-amd64-i386-libvirt-xsm blocked
test-amd64-amd64-libvirt blocked
test-arm64-arm64-libvirt blocked
test-armhf-armhf-libvirt blocked
test-amd64-i386-libvirt blocked
test-amd64-amd64-libvirt-pair blocked
test-amd64-i386-libvirt-pair blocked
test-arm64-arm64-libvirt-qcow2 blocked
test-armhf-armhf-libvirt-raw blocked
test-amd64-amd64-libvirt-vhd blocked
------------------------------------------------------------
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 16047 lines long.)
next reply other threads:[~2020-04-24 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 9:53 osstest service owner [this message]
2020-04-24 20:37 ` [libvirt test] 149773: regressions - FAIL Jim Fehlig
2020-06-04 12:51 ` Ian Jackson
2020-06-04 15:57 ` 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-149773-mainreport@xen.org \
--to=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xenproject.org \
/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.