[ovmf baseline-only test] 68539: all pass

[Platform Team regression test user <citrix-osstest@xenproject.org>]

This run is configured for baseline tests only.

flight 68539 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68539/

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 9fe9cf9acb475af9317dcdaf32a93f1cb77d95ac
baseline version:
 ovmf                 cc20411062137e5d820a33db73d41f97dae74368

Last test of basis    68538  2017-02-08 15:21:15 Z    0 days
Testing same since    68539  2017-02-08 22:50:35 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ruiyu Ni <ruiyu.ni@intel.com>
  Star Zeng <star.zeng@intel.com>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 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.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


Push not applicable.

------------------------------------------------------------
commit 9fe9cf9acb475af9317dcdaf32a93f1cb77d95ac
Author: Star Zeng <star.zeng@intel.com>
Date:   Tue Jan 17 17:58:26 2017 +0800

    SecurityPkg HashLibRouter: Avoid incorrect PcdTcg2HashAlgorithmBitmap
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=244
    
    Currently, when software HashLib (HashLibBaseCryptoRouter) and related
    HashInstanceLib instances are used, PcdTcg2HashAlgorithmBitmap is
    expected to be configured to 0 in platform dsc.
    But PcdTcg2HashAlgorithmBitmap has default value 0xFFFFFFFF in
    SecurityPkg.dec, and some platforms forget to configure it to 0 or
    still configure it to 0xFFFFFFFF in platform dsc, that will make final
    PcdTcg2HashAlgorithmBitmap value incorrect.
    
    This patch is to add CONSTRUCTOR in HashLib (HashLibBaseCryptoRouter)
    and PcdTcg2HashAlgorithmBitmap will be set to 0 in the CONSTRUCTOR.
    
    Current HASH_LIB_PEI_ROUTER_GUID HOB created in
    HashLibBaseCryptoRouterPei is shared between modules that link
    HashLibBaseCryptoRouterPei.
    To avoid mutual interference, separated HASH_LIB_PEI_ROUTER_GUID HOBs
    with gEfiCallerIdGuid Identifier will be created for those modules.
    
    This patch is also to add check in HashLib (HashLibBaseCryptoRouter)
    for the mismatch of supported HashMask between modules that may link
    different HashInstanceLib instances, warning will be reported if
    mismatch is found.
    
    Cc: Jiewen Yao <jiewen.yao@intel.com>
    Cc: Chao Zhang <chao.b.zhang@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@intel.com>
    Reviewed-by: Jiewen Yao <jiewen.yao@intel.com>
    Reviewed-by: Chao Zhang <chao.b.zhang@intel.com>

commit 00e39b0939574d7c2ce5dbd14f0aa2c1297e42fe
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date:   Mon Feb 6 10:00:33 2017 +0800

    MdeModulePkg/UefiBootManagerLib: Initialize Handle before using it
    
    BmExpandMediaDevicePath contains a bug that it uses the
    uninitialized Handle.
    
    Since the function is called when the Handle supports BlockIo
    or SimpleFileSystem, when there is no SimpleFileSystem installed
    on the Handle, BlockIo is *guaranteed* to be installed on the Handle.
    The fix initializes the Handle by locating the BlockIo protocol
    from the device path.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
    Cc: Jeff Fan <jeff.fan@intel.com>
    Reviewed-by: Sunny Wang <sunnywang@hpe.com>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel