From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [Xen-devel] [libvirt test] 149043: regressions - FAIL
Date: Thu, 26 Mar 2020 19:32:56 +0000 [thread overview]
Message-ID: <osstest-149043-mainreport@xen.org> (raw)
flight 149043 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/149043/
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 1 build-check(1) blocked n/a
test-arm64-arm64-libvirt-xsm 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt-xsm 1 build-check(1) blocked n/a
test-amd64-i386-libvirt-pair 1 build-check(1) blocked n/a
test-amd64-i386-libvirt-xsm 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a
test-armhf-armhf-libvirt-raw 1 build-check(1) blocked n/a
test-amd64-i386-libvirt 1 build-check(1) blocked n/a
test-arm64-arm64-libvirt-qcow2 1 build-check(1) blocked n/a
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a
test-arm64-arm64-libvirt 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt-pair 1 build-check(1) blocked n/a
test-armhf-armhf-libvirt 1 build-check(1) blocked n/a
test-amd64-amd64-libvirt-vhd 1 build-check(1) blocked n/a
version targeted for testing:
libvirt 17cdefe5f197030c70a0d250f3c5387b41663516
baseline version:
libvirt a1cd25b919509be2645dbe6f952d5263e0d4e4e5
Last test of basis 146182 2020-01-17 06:00:23 Z 69 days
Failing since 146211 2020-01-18 04:18:52 Z 68 days 65 attempts
Testing same since 149043 2020-03-26 04:19:43 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrea Bolognani <abologna@redhat.com>
Arnaud Patard <apatard@hupstream.com>
Boris Fiuczynski <fiuczy@linux.ibm.com>
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Collin Walling <walling@linux.ibm.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>
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>
Lin Ma <LMa@suse.com>
Marc-André Lureau <marcandre.lureau@redhat.com>
Marek Marczykowski-Górecki <marmarek@invisiblethingslab.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>
Pino Toscano <ptoscano@redhat.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>
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 11831 lines long.)
reply other threads:[~2020-03-26 19:33 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-149043-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 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).