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

[Platform Team regression test user <citrix-osstest@xxxxxxxxxxxxxx>]

This run is configured for baseline tests only.

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

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-pvops                <job status>                 broken
 build-i386-xsm                  <job status>                 broken
 build-amd64                     <job status>                 broken
 build-i386-xsm                2 hosts-allocate          broken REGR. vs. 74576
 build-amd64-pvops             2 hosts-allocate          broken REGR. vs. 74576
 build-i386                    2 hosts-allocate          broken REGR. vs. 74576
 build-i386-pvops              2 hosts-allocate          broken REGR. vs. 74576
 build-amd64-xsm               2 hosts-allocate          broken REGR. vs. 74576
 build-amd64                   2 hosts-allocate          broken REGR. vs. 74576

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-xsm               3 capture-logs           broken blocked in 74576
 build-amd64                   3 capture-logs           broken blocked in 74576
 build-i386                    3 capture-logs           broken blocked in 74576
 build-amd64-pvops             3 capture-logs           broken blocked in 74576
 build-i386-xsm                3 capture-logs           broken blocked in 74576
 build-i386-pvops              3 capture-logs           broken blocked in 74576

version targeted for testing:
 ovmf                 8b0e67821bd66af70433ee4bb858325f3033609a
baseline version:
 ovmf                 13d909f89a3cee1c1f6b851a4cda7bd1a44e90ae

Last test of basis    74576  2018-04-11 04:54:42 Z    1 days
Testing same since    74580  2018-04-12 00:49:45 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Laszlo Ersek <lersek@xxxxxxxxxx>
  Yonghong Zhu <yonghong.zhu@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.xs.citrite.net/~osstest/testlogs/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-pvops broken
broken-job build-i386-xsm broken
broken-job build-amd64 broken
broken-step build-i386-xsm hosts-allocate
broken-step build-amd64-pvops hosts-allocate
broken-step build-i386 hosts-allocate
broken-step build-i386-pvops hosts-allocate
broken-step build-amd64-xsm hosts-allocate
broken-step build-amd64 hosts-allocate
broken-step build-amd64-xsm capture-logs
broken-step build-amd64 capture-logs
broken-step build-i386 capture-logs
broken-step build-amd64-pvops capture-logs
broken-step build-i386-xsm capture-logs
broken-step build-i386-pvops capture-logs

Push not applicable.

------------------------------------------------------------
commit 8b0e67821bd66af70433ee4bb858325f3033609a
Author: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
Date:   Tue Apr 10 21:26:32 2018 +0800

    BaseTools: Fix the build error caused by eca980c0c899
    
    Roll back the fixed at build pcd collection to include the pcd in
    Module and Library.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Tested-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit 6301d2e24ab67786fa36a6d87e7a0f6625e7b831
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Tue Apr 10 19:34:50 2018 +0200

    OvmfPkg: remove BLOCK_MMIO_PROTOCOL and BlockMmioToBlockIoDxe
    
    BLOCK_MMIO_PROTOCOL and BlockMmioToBlockIoDxe were introduced to OvmfPkg
    in March 2010, in adjacent commits b0f5144676fa and efd82c5794ec. In the
    past eight years, no driver or application seems to have materialized that
    produced BLOCK_MMIO_PROTOCOL instances. Meanwhile the UEFI spec has
    developed the EFI_RAM_DISK_PROTOCOL, which edk2 implements (and OVMF
    includes) as RamDiskDxe.
    
    Rather than fixing issues in the unused BlockMmioToBlockIoDxe driver,
    remove the driver, together with the BLOCK_MMIO_PROTOCOL definition that
    now becomes unused too.
    
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Cc: Steven Shi <steven.shi@xxxxxxxxx>
    Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=926
    Reported-by: Steven Shi <steven.shi@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

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