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] 66893: tolerable trouble: blocked/broken/pass
Date: Wed, 3 Aug 2016 07:48:56 +0100 [thread overview]
Message-ID: <osstest-66893-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 66893 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/66893/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
build-amd64 3 host-install(3) broken like 66892
Tests which did not succeed, but are not blocking:
build-amd64-libvirt 1 build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-ovmf-amd64 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 846ea5f537c8f8313abb2f8f29794d13ac4becec
baseline version:
ovmf a6d594c5fabd8da2273d2794826ec086cf9c3c04
Last test of basis 66892 2016-08-03 01:49:39 Z 0 days
Testing same since 66893 2016-08-03 04:49:38 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Dong, Eric <eric.dong@intel.com>
Eric Dong <eric.dong@intel.com>
Giri P Mudusuru <giri.p.mudusuru@intel.com>
jobs:
build-amd64-xsm pass
build-i386-xsm pass
build-amd64 broken
build-i386 pass
build-amd64-libvirt blocked
build-i386-libvirt pass
build-amd64-pvops pass
build-i386-pvops pass
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-amd64 host-install(3)
Push not applicable.
------------------------------------------------------------
commit 846ea5f537c8f8313abb2f8f29794d13ac4becec
Author: Giri P Mudusuru <giri.p.mudusuru@intel.com>
Date: Mon Aug 1 16:16:30 2016 -0700
MdePkg: Add DmaRemappingReportingTable.h
DMA Remapping Reporting (DMAR) ACPI table definitions from Intel(R)
Virtualization Technology for Directed I/O (VT-D) Architecture
Specification v2.4 dated June 2016.
This replaces the DMARemappingReportingTable.h from
EdkCompatibilityPkg\Foundation\Include\IndustryStandard
Patch V2: added below defines and re-arranged the file.
EFI_ACPI_DMAR_DRHD_FLAGS_INCLUDE_PCI_ALL
EFI_ACPI_DMAR_ATSR_FLAGS_ALL_PORTS
Cc: Michael Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Jiewen Yao <jiewen.yao@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Giri P Mudusuru <giri.p.mudusuru@intel.com>
Reviewed-by: Jiewen Yao <jiewen.yao@intel.com>
Reviewed-by: Michael Kinney <michael.d.kinney@intel.com>
commit 4636e4426a31802c25bd8409be9031c4d20324f4
Author: Dong, Eric <eric.dong@intel.com>
Date: Tue Aug 2 19:32:30 2016 +0800
SecurityPkg OpalPasswordDxe: Fix buffer overflow issue.
In current code, PSID is processed as string and the length is 0x20.
Current code only reserved 0x20 length buffer for it, no extra buffer
for the '\0'. When driver call UnicodeStrToAsciiStrS to convert PSID,
it search the '\0' for the end. So extra dirty data saved in PSID
info which caused PSID revert action failed. This patch reserved
extra 1 byte data for the '\0'.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Eric Dong <eric.dong@intel.com>
Cc: Star Zeng <star.zeng@intel.com>
Reviewed-by: Star Zeng <star.zeng@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2016-08-03 6:48 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-66893-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 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).