From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [ovmf test] 153738: trouble: blocked/broken
Date: Sat, 05 Sep 2020 06:28:48 +0000 [thread overview]
Message-ID: <osstest-153738-mainreport@xen.org> (raw)
flight 153738 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/153738/
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-amd64-pvops 2 hosts-allocate broken REGR. vs. 152863
build-i386-pvops 2 hosts-allocate broken REGR. vs. 152863
build-amd64 2 hosts-allocate broken REGR. vs. 152863
build-i386-xsm 2 hosts-allocate broken REGR. vs. 152863
build-amd64-xsm 2 hosts-allocate broken REGR. vs. 152863
build-i386 2 hosts-allocate broken REGR. vs. 152863
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 2ace920de1e91e22fb9bb2ec9e15ffd5e28e70ac
baseline version:
ovmf 63d92674d240ab4ecab94f98e1e198842bb7de00
Last test of basis 152863 2020-08-26 16:09:47 Z 9 days
Failing since 152915 2020-08-27 18:09:42 Z 8 days 142 attempts
Testing same since 153709 2020-09-04 14:10:46 Z 0 days 7 attempts
------------------------------------------------------------
People who touched revisions under test:
Abner Chang <abner.chang@hpe.com>
Bob Feng <bob.c.feng@intel.com>
Laszlo Ersek <lersek@redhat.com>
Paul <paul.grimes@amd.com>
Paul G <paul.grimes@amd.com>
Qi Zhang <qi1.zhang@intel.com>
Shenglei Zhang <shenglei.zhang@intel.com>
Wenyi Xie <xiewenyi2@huawei.com>
Zhang, Shenglei <shenglei.zhang@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-amd64-pvops hosts-allocate
broken-step build-i386-pvops hosts-allocate
broken-step build-amd64 hosts-allocate
broken-step build-i386-xsm hosts-allocate
broken-step build-amd64-xsm hosts-allocate
broken-step build-i386 hosts-allocate
Not pushing.
(No revision log; it would be 321 lines long.)
reply other threads:[~2020-09-05 6:29 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-153738-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.