From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [ovmf test] 112571: regressions - FAIL
Date: Fri, 11 Aug 2017 02:02:26 +0000 [thread overview]
Message-ID: <osstest-112571-mainreport@xen.org> (raw)
flight 112571 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112571/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm 6 xen-build fail REGR. vs. 112539
build-i386 6 xen-build fail REGR. vs. 112539
build-amd64-xsm 6 xen-build fail REGR. vs. 112539
build-amd64 6 xen-build fail REGR. vs. 112539
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 42750cf1753518ec2260ef8387d34aa8a7616303
baseline version:
ovmf 7ef0dae092afcfb6fab7e8372c78097672168c4a
Last test of basis 112539 2017-08-09 16:46:45 Z 1 days
Failing since 112545 2017-08-10 04:47:25 Z 0 days 5 attempts
Testing same since 112563 2017-08-10 16:48:43 Z 0 days 2 attempts
------------------------------------------------------------
People who touched revisions under test:
Chris Ruffin <chris.ruffin@intel.com>
Huajing Li <huajing.li@intel.com>
Michael D Kinney <michael.d.kinney@intel.com>
jobs:
build-amd64-xsm fail
build-i386-xsm fail
build-amd64 fail
build-i386 fail
build-amd64-libvirt blocked
build-i386-libvirt blocked
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.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
Not pushing.
------------------------------------------------------------
commit 42750cf1753518ec2260ef8387d34aa8a7616303
Author: Michael D Kinney <michael.d.kinney@intel.com>
Date: Wed Aug 9 12:28:40 2017 -0700
QuarkPlatformPkg/Readme.md: Bring Readme.md up to date
The following commit moved the QuarkSocBinPkg from the root
directory of the edk2-non-osi repository to the
Silicon/Intel directory.
https://github.com/tianocore/edk2-non-osi/commit/182e85d04566800fe188de4b1c30a50533dd74b7
The following updates are made to Readme.md:
* PACKAGES_PATH setting for edk2-non-osi directory changes
* Remove use of edk2-FatPkg repository
* Remove use of edk2-BaseTools-win32 repository
* Run python build tools from sources
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Kelly Steele <kelly.steele@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
Reviewed-by: Kelly Steele <kelly.steele@intel.com>
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
commit 8e8cc6881836705818ee9cd70bd48c01823ded62
Author: Michael D Kinney <michael.d.kinney@intel.com>
Date: Wed Aug 9 12:19:46 2017 -0700
QuarkSocPkg/MemoryInit: Remove use of memset()/memcpy()
Map the use of memset() and memcpy() to the BaseMemoryLib
functions ZeroMem(), SetMem(), and CopyMem(). This fixes
GCC build issues with this module.
With the remap of the functions, the [BuildOptions] MSFT
CC_FLAGS to enable /Oi can also be removed, so the MSFT
and GCC builds behave the same.
Cc: Kelly Steele <kelly.steele@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
Reviewed-by: Kelly Steele <kelly.steele@intel.com>
commit 95cc9a51e1057ace27ef09b5e19fa45d3e66ef2b
Author: Chris Ruffin <chris.ruffin@intel.com>
Date: Thu Aug 3 23:37:42 2017 +0800
BaseTools/edksetup.sh: fix invalid test for current working directory
edksetup.sh implements a test that requires the current working
directory to contain the edksetup.sh script. This test has the side
effect of requiring the WORKSPACE to be set to the same directory as
the edksetup.sh. In a multiple workspace configuration, it is
required to be able to have a WORKSPACE that is different from the
directory that contains edksetup.sh. This changeset skips this test
if PACKAGE_PATH is set.
Change-Id: Ie6f16a08c012baf4e650c48cc8e91cdc466d05f2
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chris Ruffin <chris.ruffin@intel.com>
Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com>
commit d506d8db7168c2c12a9e7afe0bf9047d14ec4c54
Author: Huajing Li <huajing.li@intel.com>
Date: Mon Aug 7 15:51:43 2017 +0800
ShellPkg/driver: Show "-" in non-SFO mode
The patch shows "X"/"-" instead of "Y"/"N" in column "CFG"
and "DIAG".
The patch shows "-" instead of "0" in column "#D" and "#C".
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Huajing Li <huajing.li@intel.com>
Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
commit 416d48f755518fd1d202b97be2e9944df6e8f0d4
Author: Huajing Li <huajing.li@intel.com>
Date: Wed Aug 9 10:54:32 2017 +0800
ShellPkg/drivers: Show Image Name in non-SFO mode
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Huajing Li <huajing.li@intel.com>
Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-08-11 2:02 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-112571-mainreport@xen.org \
--to=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.