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

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

This run is configured for baseline tests only.

flight 71262 ovmf real [real]

Failures :-/ but no regressions.

Regressions which are regarded as allowable (not blocking):
 build-i386-pvops              3 host-install(3)       broken baseline untested
 build-i386-xsm                3 host-install(3)       broken baseline untested
 build-amd64-xsm               3 host-install(3)       broken baseline untested
 build-i386                    3 host-install(3)       broken baseline untested
 build-amd64-pvops             3 host-install(3)       broken baseline untested
 build-amd64                   3 host-install(3)       broken baseline untested

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                 d7b96017ccf5922b798f496fbcdcac4067d04c6d
baseline version:
 ovmf                 97cdb33b575a80ca5c20ad862331f3c6d9415575

Last test of basis    71261  2017-05-07 02:16:53 Z    1 days
Testing same since    71262  2017-05-08 03:16:38 Z    0 days    1 attempts

People who touched revisions under test:
  Star Zeng <star.zeng@xxxxxxxxx>

 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

Test harness code can be found at

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

Push not applicable.

commit d7b96017ccf5922b798f496fbcdcac4067d04c6d
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Fri May 5 16:11:57 2017 +0800

    MdePkg DxeServicesLib: Handle potential NULL FvHandle
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=514
    The FvHandle input to InternalGetSectionFromFv() may be NULL,
    then ASSERT will appear. It is because the LoadedImage->DeviceHandle
    returned from InternalImageHandleToFvHandle() may be NULL.
    For example for DxeCore, there is LoadedImage protocol installed
    for it, but the LoadedImage->DeviceHandle could not be initialized
    before the FV2 (contain DxeCore) protocol is installed.
    This patch is to update InternalGetSectionFromFv() to return
    EFI_NOT_FOUND directly for NULL FvHandle.
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Cc: Michael Turner <Michael.Turner@xxxxxxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

Xen-devel mailing list



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