* [ovmf test] 122718: regressions - FAIL
@ 2018-05-14 9:29 osstest service owner
0 siblings, 0 replies; only message in thread
From: osstest service owner @ 2018-05-14 9:29 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 122718 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122718/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt 6 libvirt-build fail REGR. vs. 122667
version targeted for testing:
ovmf c61db18e5d11e4c25e32bfb3f999a88e3207eb5f
baseline version:
ovmf 0edb7ec5ced0a28b93bf8c13b12f0a277c44dbbc
Last test of basis 122667 2018-05-09 06:53:09 Z 5 days
Testing same since 122718 2018-05-12 06:34:08 Z 2 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Bi, Dandan <dandan.bi@intel.com>
Carsey, Jaben </o=Intel/ou=Americas01/cn=Workers/cn=Carsey, Jaben>
Dandan Bi <dandan.bi@intel.com>
Derek Lin <derek.lin2@hpe.com>
Jaben Carsey <jaben.carsey@intel.com>
Lin, Derek <derek.lin2@hpe.com>
Star Zeng <star.zeng@intel.com>
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 fail
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
test-amd64-i386-xl-qemuu-ovmf-amd64 pass
------------------------------------------------------------
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 c61db18e5d11e4c25e32bfb3f999a88e3207eb5f
Author: Lin, Derek <derek.lin2@hpe.com>
Date: Wed May 9 17:03:24 2018 +0800
BaseTools: Fix python error with --genfds-multi-thread.
When self.Alignment is None, it ran into python error since there is no
strip() in None.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Derek Lin <derek.lin2@hpe.com>
Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com>
commit c731b5450576a8dd0afb1d2dd013203235395a4f
Author: Yonghong Zhu <yonghong.zhu@intel.com>
Date: Wed May 9 16:41:28 2018 +0800
BaseTools: Remove the redundant code
the ArraySize and Array already be got in line 1093, so this code are
redundant.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
commit 6b285ca3663d3c71cc68d01684a98f0d7537885e
Author: Yunhua Feng <yunhuax.feng@intel.com>
Date: Mon May 7 18:26:24 2018 +0800
BaseTools: Fix generating array's size is incorrect in AutoGen.c
case example:
DSC:
[PcdsFixedAtBuild]
PcdToken.PcdName | "A"
[Components]
TestPkg/TestDriver.inf {
PcdToken.PcdName | {0x41,0x42,0x43,0x44}
}
Generating the size of array is incorrect in AutoGen.c
GLOBAL_REMOVE_IF_UNREFERENCED const UINT8
_gPcd_FixedAtBuild_PcdName[2] = {0x41,0x42,0x43,0x44};
Fixes: https://bugzilla.tianocore.org/show_bug.cgi?id=950
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: Yonghong Zhu <yonghong.zhu@intel.com>
commit 1dc287c3a3f1f090ef6b8ff80f7b3b3725071471
Author: Carsey, Jaben </o=Intel/ou=Americas01/cn=Workers/cn=Carsey, Jaben>
Date: Wed May 9 00:01:35 2018 +0800
BaseTools: incorrect calculation for 16M
the "0x" was missing.
Cc: Liming Gao <liming.gao@intel.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jaben Carsey <jaben.carsey@intel.com>
Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com>
commit 13e3f8c03339ebc8cd25c454fca1abde098fe7ed
Author: Bi, Dandan <dandan.bi@intel.com>
Date: Wed May 9 13:02:11 2018 +0800
BaseTools/VfrCompile: Avoid using uninitialized pointer
V2:
Add function _INIT_OPHDR_COND () for variable initialization.
Make code logic more clean.
Previously _CLEAR_SAVED_OPHDR () is used for variable
initialization, and we updated it to clean memory.
But _CLEAR_SAVED_OPHDR () is still called for variable
initialization. This will cause uninitialized pointer
will be checked to free and cause unexpected issue.
This patch is to add new function for variable initialization
and keep _CLEAR_SAVED_OPHDR () to clean memory which is
aligned with its function name.
Cc: Liming Gao <liming.gao@intel.com>
Cc: Gary Lin <glin@suse.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Dandan Bi <dandan.bi@intel.com>
Reviewed-by: Eric Dong <eric.dong@intel.com>
commit e91797885aee58ae65d7935332e580dc8517e8f6
Author: Star Zeng <star.zeng@intel.com>
Date: Wed Mar 28 16:52:12 2018 +0800
IntelSiliconPkg MicrocodeUpdateDxe: Honor FIT table
It is the second step for
https://bugzilla.tianocore.org/show_bug.cgi?id=540.
V2: Use error handling instead of ASSERT for FIT table checking result.
Cc: Jiewen Yao <jiewen.yao@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Star Zeng <star.zeng@intel.com>
Reviewed-by: Jiewen Yao <jiewen.yao@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-05-14 9:29 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-05-14 9:29 [ovmf test] 122718: regressions - FAIL osstest service owner
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).