[ovmf baseline-only test] 66892: trouble: blocked/broken/pass

[ovmf baseline-only test] 66892: trouble: blocked/broken/pass

[Platform Team regression test user]

This run is configured for baseline tests only.

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

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64                   3 host-install(3)         broken REGR. vs. 66890

Tests which did not succeed, but are not blocking:
 build-amd64-libvirt           1 build-check(1)               blocked  n/a
 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

version targeted for testing:
 ovmf                 a6d594c5fabd8da2273d2794826ec086cf9c3c04
baseline version:
 ovmf                 8265373e60ad79acd4a20affe2c49470c68d6a9c

Last test of basis    66890  2016-08-02 23:20:21 Z    0 days
Testing same since    66892  2016-08-03 01:49:39 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Cinnamon Shia <cinnamon.shia@hpe.com>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  broken  
 build-i386                                                   pass    
 build-amd64-libvirt                                          blocked 
 build-i386-libvirt                                           pass    
 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.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 host-install(3)

Push not applicable.

------------------------------------------------------------
commit a6d594c5fabd8da2273d2794826ec086cf9c3c04
Author: Cinnamon Shia <cinnamon.shia@hpe.com>
Date:   Wed Aug 3 01:25:10 2016 +0800

    OvmfPkg: use StatusCode Router and Handler from MdeModulePkg
    
    In the Platform Init v1.4a spec,
    - Volume 1 "4.7 Status Code Service" defines the
      EFI_PEI_SERVICES.ReportStatusCode() service,
    - Volume 1 "6.3.5 Status Code PPI (Optional)" defines the
      EFI_PEI_PROGRESS_CODE_PPI (equivalent to the above),
    - Volume 2 "14.2 Status Code Runtime Protocol" defines the
      EFI_STATUS_CODE_PROTOCOL.
    
    These allow PEIMs and DXE (and later) modules to report status codes.
    
    Currently OvmfPkg uses modules from under
    "IntelFrameworkModulePkg/Universal/StatusCode/", which produce the above
    abstractions (PPI and PROTOCOL) directly, and write the status codes, as
    they are reported, to the serial port or to a memory buffer. This is
    called "handling" the status codes.
    
    In the Platform Init v1.4a spec,
    - Volume 3 "7.2.2 Report Status Code Handler PPI" defines
      EFI_PEI_RSC_HANDLER_PPI,
    - Volume 3 "7.2.1 Report Status Code Handler Protocol" defines
      EFI_RSC_HANDLER_PROTOCOL.
    
    These allow several PEIMs and runtime DXE drivers to register callbacks
    for status code handling.
    
    MdeModulePkg offers a PEIM under
    "MdeModulePkg/Universal/ReportStatusCodeRouter/Pei" that produces both
    EFI_PEI_PROGRESS_CODE_PPI and EFI_PEI_RSC_HANDLER_PPI, and a runtime DXE
    driver under "MdeModulePkg/Universal/ReportStatusCodeRouter/RuntimeDxe"
    that produces both EFI_STATUS_CODE_PROTOCOL and EFI_RSC_HANDLER_PROTOCOL.
    
    MdeModulePkg also offers status code handler modules under
    MdeModulePkg/Universal/StatusCodeHandler/ that depend on
    EFI_PEI_RSC_HANDLER_PPI and EFI_RSC_HANDLER_PROTOCOL, respectively.
    
    The StatusCodeHandler modules register themselves with
    ReportStatusCodeRouter through EFI_PEI_RSC_HANDLER_PPI /
    EFI_RSC_HANDLER_PROTOCOL. When another module reports a status code
    through EFI_PEI_PROGRESS_CODE_PPI / EFI_STATUS_CODE_PROTOCOL, it reaches
    the phase-matching ReportStatusCodeRouter module first, which in turn
    passes the status code to the pre-registered, phase-matching
    StatusCodeHandler module.
    
    The status code handling in the StatusCodeHandler modules is identical to
    the one currently provided by the IntelFrameworkModulePkg modules. Replace
    the IntelFrameworkModulePkg modules with the MdeModulePkg ones, so we can
    decrease our dependency on IntelFrameworkModulePkg.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Cinnamon Shia <cinnamon.shia@hpe.com>
    Suggested-by: Liming Gao <liming.gao@intel.com>
    Fixes: https://tianocore.acgmultimedia.com/show_bug.cgi?id=63
    [jordan.l.justen@intel.com: point out IntelFareworkModulePkg typos]
    Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
    [lersek@redhat.com: rewrap to 74 cols; fix IntelFareworkModulePkg typos]
    Reviewed-by: Laszlo Ersek <lersek@redhat.com>
    Regression-tested-by: Laszlo Ersek <lersek@redhat.com>

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