From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [ovmf test] 124761: trouble: blocked/broken
Date: Wed, 27 Jun 2018 16:39:43 +0000 [thread overview]
Message-ID: <osstest-124761-mainreport@xen.org> (raw)
flight 124761 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124761/
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-pvops <job status> broken
build-i386 <job status> broken
build-i386-xsm <job status> broken
build-i386-xsm 4 host-install(4) broken REGR. vs. 124618
build-i386-pvops 4 host-install(4) broken REGR. vs. 124618
build-i386 4 host-install(4) broken REGR. vs. 124618
build-amd64 4 host-install(4) broken REGR. vs. 124618
build-amd64-pvops 4 host-install(4) broken REGR. vs. 124618
build-amd64-xsm 4 host-install(4) broken REGR. vs. 124618
Tests which did not succeed, but are not blocking:
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-amd64-libvirt 1 build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
version targeted for testing:
ovmf 3c920616bb22c7f08d473ee555c1f51930aba35e
baseline version:
ovmf 3b03b5e990f8bb347dfdb91926d8ef015d0b607e
Last test of basis 124618 2018-06-22 19:10:57 Z 4 days
Failing since 124675 2018-06-24 23:40:15 Z 2 days 3 attempts
Testing same since 124761 2018-06-27 10:25:30 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Bi, Dandan <dandan.bi@intel.com>
Chao Zhang <chao.b.zhang@intel.com>
Chasel Chiu <chasel.chiu@intel.com>
Chasel, Chiu <chasel.chiu@intel.com>
Dandan Bi <dandan.bi@intel.com>
Gary Lin <glin@suse.com>
Hao Wu <hao.a.wu@intel.com>
Jaben Carsey <jaben.carsey@intel.com>
Liming Gao <liming.gao@intel.com>
Michael D Kinney <michael.d.kinney@intel.com>
Star Zeng <star.zeng@intel.com>
Thomas Palmer <thomas.palmer@hpe.com>
Xu WeiX <weix.xu@intel.com>
Zhang, Chao B <chao.b.zhang@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-pvops broken
broken-job build-i386 broken
broken-job build-i386-xsm broken
broken-step build-i386-xsm host-install(4)
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-amd64-xsm host-install(4)
Not pushing.
(No revision log; it would be 660 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2018-06-27 16:39 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-124761-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.