From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [ovmf baseline-only test] 83876: trouble: blocked/broken
Date: Fri, 5 Apr 2019 11:15:29 +0100 [thread overview]
Message-ID: <osstest-83876-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 83876 ovmf real [real]
http://osstest.xensource.com/osstest/logs/83876/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm <job status> broken
build-i386 <job status> broken
build-amd64-pvops <job status> broken
build-i386-xsm <job status> broken
build-amd64 <job status> broken
build-i386-pvops <job status> broken
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
build-amd64-libvirt 1 build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
build-i386-libvirt 1 build-check(1) blocked n/a
build-i386-pvops 4 host-install(4) broken baseline untested
build-i386 4 host-install(4) broken baseline untested
build-amd64 4 host-install(4) broken baseline untested
build-amd64-pvops 4 host-install(4) broken baseline untested
build-i386-xsm 4 host-install(4) broken baseline untested
build-amd64-xsm 4 host-install(4) broken baseline untested
version targeted for testing:
ovmf 7ed72121b753a7493a8c5bf3711b5efbc5e80491
baseline version:
ovmf b02873340b2de5c2fe8325d22214cd3a5b21c5e5
Last test of basis 83865 2019-04-03 15:27:06 Z 1 days
Testing same since 83876 2019-04-05 08:53:59 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Bret Barkelew <Bret.Barkelew@microsoft.com>
Laszlo Ersek <lersek@redhat.com>
Liming Gao <liming.gao@intel.com>
Shenglei Zhang <shenglei.zhang@intel.com>
Zhang, Shenglei <shenglei.zhang@intel.com>
Zhichao Gao <zhichao.gao@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.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images
Logs, config files, etc. are available at
http://osstest.xensource.com/osstest/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
broken-job build-amd64-xsm broken
broken-job build-i386 broken
broken-job build-amd64-pvops broken
broken-job build-i386-xsm broken
broken-job build-amd64 broken
broken-job build-i386-pvops broken
broken-step build-i386-pvops host-install(4)
broken-step build-i386 host-install(4)
broken-step build-amd64 host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-i386-xsm host-install(4)
broken-step build-amd64-xsm host-install(4)
Push not applicable.
(No revision log; it would be 686 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: <xen-devel@lists.xenproject.org>, <osstest-admin@xenproject.org>
Subject: [Xen-devel] [ovmf baseline-only test] 83876: trouble: blocked/broken
Date: Fri, 5 Apr 2019 11:15:29 +0100 [thread overview]
Message-ID: <osstest-83876-mainreport@xen.org> (raw)
Message-ID: <20190405101529.7SE1gETG6t_nC3M5-1b2eqNPs44ojQUlTbj3ElHMgOA@z> (raw)
This run is configured for baseline tests only.
flight 83876 ovmf real [real]
http://osstest.xensource.com/osstest/logs/83876/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm <job status> broken
build-i386 <job status> broken
build-amd64-pvops <job status> broken
build-i386-xsm <job status> broken
build-amd64 <job status> broken
build-i386-pvops <job status> broken
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
build-amd64-libvirt 1 build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
build-i386-libvirt 1 build-check(1) blocked n/a
build-i386-pvops 4 host-install(4) broken baseline untested
build-i386 4 host-install(4) broken baseline untested
build-amd64 4 host-install(4) broken baseline untested
build-amd64-pvops 4 host-install(4) broken baseline untested
build-i386-xsm 4 host-install(4) broken baseline untested
build-amd64-xsm 4 host-install(4) broken baseline untested
version targeted for testing:
ovmf 7ed72121b753a7493a8c5bf3711b5efbc5e80491
baseline version:
ovmf b02873340b2de5c2fe8325d22214cd3a5b21c5e5
Last test of basis 83865 2019-04-03 15:27:06 Z 1 days
Testing same since 83876 2019-04-05 08:53:59 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Bret Barkelew <Bret.Barkelew@microsoft.com>
Laszlo Ersek <lersek@redhat.com>
Liming Gao <liming.gao@intel.com>
Shenglei Zhang <shenglei.zhang@intel.com>
Zhang, Shenglei <shenglei.zhang@intel.com>
Zhichao Gao <zhichao.gao@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.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images
Logs, config files, etc. are available at
http://osstest.xensource.com/osstest/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
broken-job build-amd64-xsm broken
broken-job build-i386 broken
broken-job build-amd64-pvops broken
broken-job build-i386-xsm broken
broken-job build-amd64 broken
broken-job build-i386-pvops broken
broken-step build-i386-pvops host-install(4)
broken-step build-i386 host-install(4)
broken-step build-amd64 host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-i386-xsm host-install(4)
broken-step build-amd64-xsm host-install(4)
Push not applicable.
(No revision log; it would be 686 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-04-05 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 10:15 Platform Team regression test user [this message]
2019-04-05 10:15 ` [Xen-devel] [ovmf baseline-only test] 83876: trouble: blocked/broken Platform Team regression test user
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-83876-mainreport@xen.org \
--to=citrix-osstest@xenproject.org \
--cc=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).