* [ovmf baseline-only test] 75001: tolerable FAIL
@ 2018-07-24 16:30 Platform Team regression test user
0 siblings, 0 replies; only message in thread
From: Platform Team regression test user @ 2018-07-24 16:30 UTC (permalink / raw)
To: xen-devel, osstest-admin
This run is configured for baseline tests only.
flight 75001 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75001/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail like 74999
test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail like 74999
version targeted for testing:
ovmf 5b73e17fb17c6935d894b0084f32421e717c247f
baseline version:
ovmf 005c855dc6be0f61f76de0d7ec4a62ee737518d6
Last test of basis 74999 2018-07-24 05:19:57 Z 0 days
Testing same since 75001 2018-07-24 14:52:20 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Yonghong Zhu <yonghong.zhu@intel.com>
Yunhua Feng <yunhuax.feng@intel.com>
jobs:
build-amd64-xsm pass
build-i386-xsm pass
build-amd64 pass
build-i386 pass
build-amd64-libvirt pass
build-i386-libvirt pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 fail
test-amd64-i386-xl-qemuu-ovmf-amd64 fail
------------------------------------------------------------
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
Push not applicable.
------------------------------------------------------------
commit 5b73e17fb17c6935d894b0084f32421e717c247f
Author: Yunhua Feng <yunhuax.feng@intel.com>
Date: Fri Jul 20 15:51:39 2018 +0800
BaseTools: Fix the different token with the same PCD
If the different token with the same PCD names are used in the driver,
build can pass. If the different token with the same PCD name are used
in the different library, then the driver build will fail. The reason
is that the driver autogen.c is not generated correctly for the second
case. BaseTools should check the duplicated PCD name is the driver and
its linked libraries.
Cc: Liming Gao <liming.gao@intel.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Yunhua Feng <yunhuax.feng@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
commit bfa7eeb61d94623ddbe43b916a0bb1dc0f73a292
Author: Yonghong Zhu <yonghong.zhu@intel.com>
Date: Mon Jul 23 11:58:22 2018 +0800
BaseTools: Correct _PCD_PATCHABLE_TokenName_SIZE's value
current if user use PatchPcdSetPtr in library, it will report the
_PCD_PATCHABLE_TokenName_SIZE is not defined.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-07-24 16:30 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-07-24 16:30 [ovmf baseline-only test] 75001: tolerable FAIL Platform Team regression test user
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).