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] 75558: tolerable FAIL
Date: Fri, 2 Nov 2018 04:10:33 +0000 [thread overview]
Message-ID: <osstest-75558-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 75558 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75558/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
build-amd64-libvirt 6 libvirt-build fail like 75556
test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail like 75556
build-i386-libvirt 6 libvirt-build fail like 75556
test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail like 75556
version targeted for testing:
ovmf d3d97b378fe4d0bfbcbdb296d06bcf1d09165480
baseline version:
ovmf fd950156738ce878c0ba29af99da2ffcac5168e1
Last test of basis 75556 2018-11-01 09:00:43 Z 0 days
Testing same since 75558 2018-11-01 14:32:17 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Ruiyu Ni <ruiyu.ni@intel.com>
Tomas Pilar <tpilar@solarflare.com>
Zhiju.Fan <zhijux.fan@intel.com>
zhijufan <zhijux.fan@intel.com>
jobs:
build-amd64-xsm pass
build-i386-xsm pass
build-amd64 pass
build-i386 pass
build-amd64-libvirt fail
build-i386-libvirt fail
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 d3d97b378fe4d0bfbcbdb296d06bcf1d09165480
Author: zhijufan <zhijux.fan@intel.com>
Date: Wed Oct 17 13:57:01 2018 +0800
BaseTools: Add special handle for '\' use in Pcd Value
V2: Follow PEP8 to not multiples import on one line
Case:
gEfiOzmosisPkgTokenSpaceGuid.PcdBootLogFolderPath|L"\\Logs\\"|VOID*|12
Fixes: https://bugzilla.tianocore.org/show_bug.cgi?id=1287
Cc: Liming Gao <liming.gao@intel.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Zhiju.Fan <zhijux.fan@intel.com>
Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
commit 5b9639e697350c9e18e98ddb0119e8598b004a8f
Author: Tomas Pilar <tpilar@solarflare.com>
Date: Tue Oct 30 00:52:53 2018 +0800
BaseTools: Fix merge in FDF parser for OptionROM override
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Tomas Pilar <tpilar@solarflare.com>
Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com>
commit bfc87aa78e77ed15b09d1b4499c5eab63e8842bb
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date: Mon Oct 22 17:03:07 2018 +0800
MdeModulePkg/PiSmmIpl: Do not reset SMRAM to UC when CPU driver runs
Today's PiSmmIpl implementation initially sets SMRAM to WB to speed
up the SMM core/modules loading before SMM CPU driver runs.
When SMM CPU driver runs, PiSmmIpl resets the SMRAM to UC. It's done
in SmmIplDxeDispatchEventNotify(). COMM_BUFFER_SMM_DISPATCH_RESTART
is returned from SMM core that SMM CPU driver is just dispatched.
Since now the SMRR is widely used to control the SMRAM cache setting.
It's not needed to reset the SMRAM to UC anymore.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
Reviewed-by: Jiewen Yao <jiewen.yao@intel.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
reply other threads:[~2018-11-02 4:10 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-75558-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).