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] 71264: tolerable trouble: blocked/broken/fail/pass
Date: Mon, 8 May 2017 16:34:01 +0100 [thread overview]
Message-ID: <osstest-71264-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 71264 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71264/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
build-amd64-xsm 3 host-install(3) broken baseline untested
build-amd64-pvops 3 host-install(3) broken baseline untested
build-amd64 3 host-install(3) broken baseline untested
build-i386-libvirt 5 libvirt-build fail baseline untested
Tests which did not succeed, but are not blocking:
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
build-amd64-libvirt 1 build-check(1) blocked n/a
version targeted for testing:
ovmf 3654c4623c9b37ddc64426995fa399d8626b7ced
baseline version:
ovmf d7b96017ccf5922b798f496fbcdcac4067d04c6d
Last test of basis 71262 2017-05-08 03:16:38 Z 0 days
Testing same since 71264 2017-05-08 08:17:59 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Jeff Fan <jeff.fan@intel.com>
Ruiyu Ni <ruiyu.ni@intel.com>
jobs:
build-amd64-xsm broken
build-i386-xsm pass
build-amd64 broken
build-i386 pass
build-amd64-libvirt blocked
build-i386-libvirt fail
build-amd64-pvops broken
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-xsm host-install(3)
broken-step build-amd64-pvops host-install(3)
broken-step build-amd64 host-install(3)
Push not applicable.
------------------------------------------------------------
commit 3654c4623c9b37ddc64426995fa399d8626b7ced
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date: Fri May 5 10:10:00 2017 +0800
UefiCpuPkg/MtrrLib: Don't report OutOfResource when MTRR is enough
The MTRR calculation algorithm contains a bug that when left
subtraction cannot produce better MTRR solution, it forgets
to restore the BaseAddress/Length so that MtrrLibGetMtrrNumber()
returns bigger value of actual required MTRR numbers.
As a result, the MtrrLib reports OutOfResource but actually the
MTRR is enough.
MEMORY_RANGE mC[] = {
0, 0x100000, CacheUncacheable,
0x100000, 0x89F00000, CacheWriteBack,
0x8A000000, 0x75000000, CacheUncacheable,
0xFF000000, 0x01000000, CacheWriteProtected,
0x100000000, 0x7F00000000, CacheUncacheable,
0xFC240000, 0x2000, CacheWriteCombining // <-- trigger the error
};
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
Reviewed-by: Jeff Fan <jeff.fan@intel.com>
commit 007b51e180d2202637dfc6d2afbe8a34704c423f
Author: Jeff Fan <jeff.fan@intel.com>
Date: Mon May 8 13:31:00 2017 +0800
UefiCpuPkg: Update package version to 0.80
Cc: Feng Tian <feng.tian@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jeff Fan <jeff.fan@intel.com>
Reviewed-by: Eric Dong <eric.dong@intel.com>
commit 93041972617af5f538fac8291e7a57b7766c6e10
Author: Jeff Fan <jeff.fan@intel.com>
Date: Mon May 8 11:31:50 2017 +0800
UefiCpuPkg: Update package version to 0.80
Cc: Feng Tian <feng.tian@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jeff Fan <jeff.fan@intel.com>
Reviewed-by: Eric Dong <eric.dong@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-05-08 15:34 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-71264-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).