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

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

This run is configured for baseline tests only.

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

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                 b06dfd40bb5cf9fdd626a79a300253f193b600ae
baseline version:
 ovmf                 cfd10276ce747129bb26410bc00ac13ae1cd5d6f

Last test of basis    75224  2018-09-14 22:50:19 Z    3 days
Testing same since    75241  2018-09-18 09:50:37 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Star Zeng <star.zeng@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 b06dfd40bb5cf9fdd626a79a300253f193b600ae
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Thu Sep 13 14:27:47 2018 +0800

    IntelSiliconPkg IntelVTdDxe: Check HeaderType if func 0 is implemented
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1169
    
    Current code checks HeaderType of Function 0 even Function 0 is not
    implemented. HeaderType value will be 0xFF if Function 0 is not
    implemented, then MaxFunction will be set to PCI_MAX_FUNC + 1.
    
    The code can be optimized to only check HeaderType if Function 0 is
    implemented.
    
    Test done:
    With this patch, the result is same with the result after the patch at
    https://lists.01.org/pipermail/edk2-devel/2018-September/029623.html.
    
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Cc: Rangasai V Chaganty <rangasai.v.chaganty@xxxxxxxxx>
    Cc: Tomson Chang <tomson.chang@xxxxxxxxx>
    Cc: Jenny Huang <jenny.huang@xxxxxxxxx>
    Cc: Amy Chan <amy.chan@xxxxxxxxx>
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>

commit e69d7e99e77d2f7aa1390502d8b42d61f9aeb99a
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Thu Sep 13 10:07:30 2018 +0800

    IntelSiliconPkg IntelVTdDxe: Optimize when func 0 is not implemented
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1169
    
    PCI spec:
    They are also required to always implement function 0 in the device.
    Implementing other functions is optional and may be assigned in any
    order (i.e., a two-function device must respond to function 0 but
    can choose any of the other possible function numbers (1-7) for the
    second function).
    
    This patch updates ScanPciBus() to not scan other functions if
    function 0 is not implemented.
    
    Test done:
    Added debug code below in the second loop of ScanPciBus(),
    compared the debug logs with and without this patch, many
    non-0 unimplemented functions are skipped correctly.
    
      DEBUG ((
        DEBUG_INFO,
        "%a() B%02xD%02xF%02x VendorId: %04x DeviceId: %04x\n",
        __FUNCTION__,
        Bus,
        Device,
        Function,
        VendorID,
        DeviceID
        ));
    
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Cc: Rangasai V Chaganty <rangasai.v.chaganty@xxxxxxxxx>
    Cc: Tomson Chang <tomson.chang@xxxxxxxxx>
    Cc: Jenny Huang <jenny.huang@xxxxxxxxx>
    Cc: Amy Chan <amy.chan@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>

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