[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [ovmf baseline-only test] 75295: trouble: blocked/broken



This run is configured for baseline tests only.

flight 75295 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75295/

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-xsm                 <job status>                 broken
 build-i386                      <job status>                 broken
 build-amd64-pvops               <job status>                 broken
 build-i386-xsm                  <job status>                 broken
 build-amd64                     <job status>                 broken
 build-i386-pvops                <job status>                 broken

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
 build-amd64                   4 host-install(4)       broken baseline untested
 build-amd64-xsm               4 host-install(4)       broken baseline untested
 build-i386-pvops              4 host-install(4)       broken baseline untested
 build-i386                    4 host-install(4)       broken baseline untested
 build-amd64-pvops             4 host-install(4)       broken baseline untested
 build-i386-xsm                4 host-install(4)       broken baseline untested

version targeted for testing:
 ovmf                 2939283f2df3b8a0871e9bc7b2dd3718146318f4
baseline version:
 ovmf                 e5cd809087e5710e019d2766fab13c59a2e2ac28

Last test of basis    75292  2018-09-26 02:50:19 Z    0 days
Testing same since    75295  2018-09-26 08:32:21 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Jian J Wang <jian.j.wang@xxxxxxxxx>
  shenglei <shenglei.zhang@xxxxxxxxx>
  Zhang, Shenglei <shenglei.zhang@xxxxxxxxx>

jobs:
 build-amd64-xsm                                              broken  
 build-i386-xsm                                               broken  
 build-amd64                                                  broken  
 build-i386                                                   broken  
 build-amd64-libvirt                                          blocked 
 build-i386-libvirt                                           blocked 
 build-amd64-pvops                                            broken  
 build-i386-pvops                                             broken  
 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.xensource.com/osstest/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary

broken-job build-amd64-xsm broken
broken-job build-i386 broken
broken-job build-amd64-pvops broken
broken-job build-i386-xsm broken
broken-job build-amd64 broken
broken-job build-i386-pvops broken
broken-step build-amd64 host-install(4)
broken-step build-amd64-xsm host-install(4)
broken-step build-i386-pvops host-install(4)
broken-step build-i386 host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-i386-xsm host-install(4)

Push not applicable.

------------------------------------------------------------
commit 2939283f2df3b8a0871e9bc7b2dd3718146318f4
Author: Jian J Wang <jian.j.wang@xxxxxxxxx>
Date:   Tue Sep 18 15:17:11 2018 +0800

    UefiCpuPkg/CpuMpPei: fix vs2012 build error
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1166
    
    Visual Studio 2012 will complain uninitialized variable, StackBase,
    in the CpuPaging.c. This patch adds code to init it to zero and
    ASSERT check against 0. This is enough since uninit case will only
    happen during retrieving stack memory via gEfiHobMemoryAllocStackGuid.
    But this HOB will always be created in advance.
    
    Cc: Dandan Bi <dandan.bi@xxxxxxxxx>
    Cc: Hao A Wu <hao.a.wu@xxxxxxxxx>
    Cc: Eric Dong <eric.dong@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Jian J Wang <jian.j.wang@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Eric Dong <eric.dong@xxxxxxxxx>

commit 5267926134d17e86672b84fd57b438f05ffa68e1
Author: Jian J Wang <jian.j.wang@xxxxxxxxx>
Date:   Tue Sep 25 16:49:19 2018 +0800

    MdeModulePkg/DxeIpl: support more NX related PCDs
    
    BZ#1116: https://bugzilla.tianocore.org/show_bug.cgi?id=1116
    
    Currently IA32_EFER.NXE is only set against PcdSetNxForStack. This
    confuses developers because following two other PCDs also need NXE
    to be set, but actually not.
    
        PcdDxeNxMemoryProtectionPolicy
        PcdImageProtectionPolicy
    
    This patch solves this issue by adding logic to enable IA32_EFER.NXE
    if any of those PCDs have anything enabled.
    
    Cc: Star Zeng <star.zeng@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Jian J Wang <jian.j.wang@xxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

commit b888c57a053f41b33fcaa13da66f8de470e9a1c8
Author: Jian J Wang <jian.j.wang@xxxxxxxxx>
Date:   Fri Sep 14 10:01:28 2018 +0800

    MdeModulePkg/MdeModulePkg.dec/.uni: clarify PCDs usage
    
    BZ#1116: https://bugzilla.tianocore.org/show_bug.cgi?id=1116
    
    The usage of following PCDs described in MdeModulePkg.dec don't match
    the implementation exactly. This patch updates related description in
    both .dec and .uni files to avoid confusion in platform configuration.
    
      PcdSetNxForStack
      PcdImageProtectionPolicy
      PcdDxeNxMemoryProtectionPolicy
    
    The main change is at the statement on how to handle the FALSE or 0
    setting value in those PCDs. Current statement says the implementation
    should unset or disable related features but in fact the related code
    just do nothing (leave it to AS-IS). That means the result might be
    disabled, or might be not. It depends on other features or platform
    policy.
    
    For example, if one don't want to enforce NX onto stack memory, he/she
    needs to set PcdSetNxForStack to FALSE as well as to clear BIT4 of
    PcdDxeNxMemoryProtectionPolicy.
    
    Cc: Star Zeng <star.zeng@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Jian J Wang <jian.j.wang@xxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

commit 67998a547e47b231533f5b6668ac352f6c69104b
Author: Zhang, Shenglei <shenglei.zhang@xxxxxxxxx>
Date:   Tue Sep 25 11:51:14 2018 +0800

    UefiCpuPkg SecCore:Add a GUID removed previously
    
    The Guid gPeiSecPerformancePpiGuid removed previously
    is added into SecCore.inf.
    https://bugzilla.tianocore.org/show_bug.cgi?id=1203
    
    Cc: Eric Dong <eric.dong@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: shenglei <shenglei.zhang@xxxxxxxxx>
    Reviewed-by: Eric Dong <eric.dong@xxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.