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

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

This run is configured for baseline tests only.

flight 75205 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75205/

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

version targeted for testing:
 ovmf                 5c9ac43f47865bb9b13608fd7ae1d39ab73ef397
baseline version:
 ovmf                 1ad635b283812283e8db457ba4809d5d38433f17

Last test of basis    75200  2018-09-11 15:50:18 Z    0 days
Testing same since    75205  2018-09-12 08:20:22 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ruiyu Ni <ruiyu.ni@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.xensource.com/osstest/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-xsm broken
broken-job build-amd64 broken
broken-job build-i386-pvops broken
broken-step build-i386 host-install(4)
broken-step build-i386-pvops host-install(4)
broken-step build-i386-xsm host-install(4)
broken-step build-amd64-xsm host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-amd64 host-install(4)

Push not applicable.

------------------------------------------------------------
commit 5c9ac43f47865bb9b13608fd7ae1d39ab73ef397
Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
Date:   Wed Apr 11 11:37:08 2018 +0800

    MdeModulePkg/ConPlatform: Support short-form USB device path
    
    Today's implementation does an exact device path match to check
    whether the device path of a console is in ConIn/ConOut/ErrOut.
    But that doesn't work for the USB keyboard.
    Because when a platform have multiple USB port, ConIn needs to
    carry all device paths corresponding to each port.
    Even worse, today's BDS core logic removes the device path from
    ConIn/ConOut/ErrOut when the connection to that device path fails.
    So if user switches the USB keyboard from one port to another across
    boot, the USB keyboard doesn't work in the second boot.
    
    ConPlatform driver solved this problem by adding the
    IsHotPlugDevice() function. So that for USB keyboard, ConPlatform
    doesn't care whether its device path is in ConIn or not.
    But the rule is too loose, and now causes platform BDS cannot control
    whether to enable USB keyboard as an active console.
    
    The patch changes ConPlatform to support USB short-form device path
    when checking whether the device path of a console is in
    ConIn/ConOut/ErrOut.
    
    The logic to always accept USB/PCCARD device as active console is
    removed.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Cc: Hao A Wu <hao.a.wu@xxxxxxxxx>
    Cc: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

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