From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [ovmf baseline-only test] 71261: trouble: blocked/broken
Date: Sun, 7 May 2017 08:11:44 +0100 [thread overview]
Message-ID: <osstest-71261-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 71261 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71261/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REGR. vs. 71260
build-i386-xsm 3 host-install(3) broken REGR. vs. 71260
build-amd64-xsm 3 host-install(3) broken REGR. vs. 71260
build-i386 3 host-install(3) broken REGR. vs. 71260
build-amd64-pvops 3 host-install(3) broken REGR. vs. 71260
build-amd64 3 host-install(3) broken REGR. vs. 71260
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
version targeted for testing:
ovmf 97cdb33b575a80ca5c20ad862331f3c6d9415575
baseline version:
ovmf 0c79471d6a986b858c35dc577eaeb344cc5c4cdd
Last test of basis 71260 2017-05-06 14:49:14 Z 0 days
Testing same since 71261 2017-05-07 02:16:53 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Yonghong Zhu <yonghong.zhu@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.xs.citrite.net/~osstest/testlogs/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
broken-step build-i386-pvops host-install(3)
broken-step build-i386-xsm host-install(3)
broken-step build-amd64-xsm host-install(3)
broken-step build-i386 host-install(3)
broken-step build-amd64-pvops host-install(3)
broken-step build-amd64 host-install(3)
Push not applicable.
------------------------------------------------------------
commit 97cdb33b575a80ca5c20ad862331f3c6d9415575
Author: Yonghong Zhu <yonghong.zhu@intel.com>
Date: Wed May 3 15:19:21 2017 +0800
BaseTools: PCD can only use single access method by source build
Add the error check that A PCD can only use one type for all source
modules.
Cc: Liming Gao <liming.gao@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-05-07 7:11 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-71261-mainreport@xen.org \
--to=citrix-osstest@xenproject.org \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.com \
/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.