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

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

This run is configured for baseline tests only.

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

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

version targeted for testing:
 ovmf                 a2e61f341d26a78751b2f19b5004c6bbfc8b4fa9
baseline version:
 ovmf                 7b500c606ad101fad52327318af37889048cd45e

Last test of basis    75452  2018-10-19 04:20:43 Z    0 days
Testing same since    75458  2018-10-19 12:23:41 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Chasel Chiu <chasel.chiu@xxxxxxxxx>
  Chasel, Chiu <chasel.chiu@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-amd64 host-install(4)
broken-step build-i386-pvops host-install(4)
broken-step build-i386-xsm host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-amd64-xsm host-install(4)

Push not applicable.

------------------------------------------------------------
commit a2e61f341d26a78751b2f19b5004c6bbfc8b4fa9
Author: Chasel, Chiu <chasel.chiu@xxxxxxxxx>
Date:   Thu Oct 11 21:22:12 2018 +0800

    IntelFsp2Pkg: Support FSP Dispatch mode
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1241
    
    Add support for both API (original mode) and DISPATCH mode:
    1. Add FspMode field from reserved byte of Global
       Data Structure to tell which mode is selected by boot
       loader. If boot loader invoking FSP-M API this field
       will remain as default 0 (API mode), otherwise platform
       FSP should set this field to 1 (Dispatch mode) when
       initializing Global Data Structure.
    2. gFspInApiModePpiGuid will be instaled when FSP running in API
       mode and modules only for API mode should have this in depex.
    3. If it is DISPATCH mode, FSP will return to PEI dispatcher,
       not directly return to boot loader.
    4. DISPATCH mode supports DXE NotifyPhase drivers so FSP
       will not wait for PEI NotifyPhase callbacks, instead it
       will install gFspReadyForNotifyPhasePpiGuid PPI for
       platform to complete late initialization before transferring
       to DXE.
    
    Test: Verified FSP API and DISPATCH modes on 2 internal
          platforms and both boot successfully.
    
    Cc: Jiewen Yao <Jiewen.yao@xxxxxxxxx>
    Cc: Desimone Nathaniel L <nathaniel.l.desimone@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Chasel Chiu <chasel.chiu@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <Jiewen.yao@xxxxxxxxx>

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