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

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

This run is configured for baseline tests only.

flight 75394 ovmf real [real]

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

version targeted for testing:
 ovmf                 b9c055f72b9dbc9cef3a65b9a4932ad6e4f403e0
baseline version:
 ovmf                 2730470f9d3bbaed51a04a11bfc1bf21670fa49e

Last test of basis    75389  2018-10-11 00:20:25 Z    0 days
Testing same since    75394  2018-10-11 10:20:15 Z    0 days    1 attempts

People who touched revisions under test:
  Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
  Chasel Chiu <chasel.chiu@xxxxxxxxx>
  Chasel, Chiu <chasel.chiu@xxxxxxxxx>
  Marcin Wojtas <mw@xxxxxxxxxxxx>

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

Push not applicable.

commit b9c055f72b9dbc9cef3a65b9a4932ad6e4f403e0
Author: Chasel, Chiu <chasel.chiu@xxxxxxxxx>
Date:   Mon Oct 8 15:44:45 2018 +0800

    IntelFsp2Pkg/GenCfgOpt.py: Support PCD input from command line
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1231
    Build system already support override PCD value by command
    line so add this support to GenCfgOpt.py
    Also update revision to 0.53
    Test: Verified UPD header files generated can reflect different
          PCD values from --pcd build command input
    Cc: Jiewen Yao <Jiewen.yao@xxxxxxxxx>
    Cc: Gao Liming <liming.gao@xxxxxxxxx>
    Cc: Zhu Yonghong <yonghong.zhu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Chasel Chiu <chasel.chiu@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <Jiewen.yao@xxxxxxxxx>
    Reviewed-by: Zhu Yonghong <yonghong.zhu@xxxxxxxxx>

commit 1a3bee20820c9f68a235a31ccc92db1f299266c9
Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
Date:   Wed Oct 10 10:34:50 2018 +0200

    MdeModulePkg/NonDiscoverablePciDeviceDxe: expose unique B/D/F identifiers
    Currently, the implementation of EFI_PCI_IO_PROTOCOL::GetLocation()
    in NonDiscoverablePciDeviceDxe returns the same set of dummy values
    for each instance of the NON_DISCOVERABLE_DEVICE protocol that it
    attaches itself to. However, this turns out to be causing problems
    in cases where software (such as the ARM Compliance Test Suite [ACS])
    attempts to use these values to uniquely identify controllers, since
    the collisions create ambiguity in this regard.
    So let's modify GetLocation() to return an arbitrary bus/device tuple
    on segment 0xff instead. This is guaranteed not to clash with other
    non-discoverable PCI devices, and highly unlikely to clash with real
    PCIe devices.
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Tested-by: Marcin Wojtas <mw@xxxxxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

Xen-devel mailing list



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