From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [ovmf test] 162926: trouble: blocked/broken
Date: Mon, 21 Jun 2021 11:32:50 +0000 [thread overview]
Message-ID: <osstest-162926-mainreport@xen.org> (raw)
flight 162926 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162926/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 <job status> broken
build-amd64-pvops <job status> broken
build-amd64-xsm <job status> broken
build-i386 <job status> broken
build-i386-pvops <job status> broken
build-i386-xsm <job status> broken
build-i386 4 host-install(4) broken REGR. vs. 162359
build-i386-pvops 4 host-install(4) broken REGR. vs. 162359
build-i386-xsm 4 host-install(4) broken REGR. vs. 162359
build-amd64-xsm 4 host-install(4) broken REGR. vs. 162359
build-amd64-pvops 4 host-install(4) broken REGR. vs. 162359
build-amd64 4 host-install(4) broken REGR. vs. 162359
Tests which did not succeed, but are not blocking:
build-amd64-libvirt 1 build-check(1) blocked n/a
build-i386-libvirt 1 build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
version targeted for testing:
ovmf a63914d3f603580e5aeceb5edbafe56688210141
baseline version:
ovmf c410ad4da4b7785170d3d42a3ba190c2caac6feb
Last test of basis 162359 2021-06-04 03:40:08 Z 17 days
Failing since 162368 2021-06-04 15:42:59 Z 16 days 37 attempts
Testing same since 162900 2021-06-19 07:19:12 Z 2 days 5 attempts
------------------------------------------------------------
People who touched revisions under test:
Ard Biesheuvel <ardb@kernel.org>
gaoliming <gaoliming@byosoft.com.cn>
Hao A Wu <hao.a.wu@intel.com>
Jian J Wang <jian.j.wang@intel.com>
Kaaira Gupta <kaaira7319@gmail.com>
Kun Qin <kuqin12@gmail.com>
Laszlo Ersek <lersek@redhat.com>
Leif Lindholm <leif@nuviainc.com>
Liming Gao <gaoliming@byosoft.com.cn>
Maurice Ma <maurice.ma@intel.com>
Ni, Ray <ray.ni@intel.com>
Patrick Rudolph <patrick.rudolph@9elements.com>
Ray Ni <ray.ni@intel.com>
Rebecca Cran <rebecca@nuviainc.com>
Scottie Kuo <scottie.kuo@intel.com>
Sean Brogan <sean.brogan@microsoft.com>
Sean Brogan <spbrogan@live.com>
Sumana Venur <sumana.venur@intel.com>
Zhiguang Liu <zhiguang.liu@intel.com>
jobs:
build-amd64-xsm broken
build-i386-xsm broken
build-amd64 broken
build-i386 broken
build-amd64-libvirt blocked
build-i386-libvirt blocked
build-amd64-pvops broken
build-i386-pvops broken
test-amd64-amd64-xl-qemuu-ovmf-amd64 blocked
test-amd64-i386-xl-qemuu-ovmf-amd64 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
broken-job build-amd64 broken
broken-job build-amd64-pvops broken
broken-job build-amd64-xsm broken
broken-job build-i386 broken
broken-job build-i386-pvops broken
broken-job build-i386-xsm broken
broken-step build-i386 host-install(4)
broken-step build-i386-pvops host-install(4)
broken-step build-i386-xsm host-install(4)
broken-step build-amd64-xsm host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-amd64 host-install(4)
Not pushing.
(No revision log; it would be 2173 lines long.)
reply other threads:[~2021-06-21 11: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-162926-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.