[ovmf baseline-only test] 71107: trouble: blocked/broken

[Platform Team regression test user <citrix-osstest@xenproject.org>]

This run is configured for baseline tests only.

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

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-i386-pvops              3 host-install(3)         broken REGR. vs. 71096
 build-amd64-xsm               3 host-install(3)         broken REGR. vs. 71096
 build-amd64-pvops             3 host-install(3)         broken REGR. vs. 71096
 build-amd64                   3 host-install(3)         broken REGR. vs. 71096
 build-i386                    3 host-install(3)         broken REGR. vs. 71096
 build-i386-xsm                3 host-install(3)         broken REGR. vs. 71096

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

version targeted for testing:
 ovmf                 d590cce5cd9b9d31848eda4fcb62d1ab3fd05dfd
baseline version:
 ovmf                 647636e1750b07110ed807f455cb9c8b7d089f75

Last test of basis    71096  2017-03-25 03:53:53 Z    2 days
Testing same since    71107  2017-03-27 05:57:58 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Derek Lin <derek.lin2@hpe.com>
  Yonghong Zhu <yonghong.zhu@intel.com>

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

Push not applicable.

------------------------------------------------------------
commit d590cce5cd9b9d31848eda4fcb62d1ab3fd05dfd
Author: Yonghong Zhu <yonghong.zhu@intel.com>
Date:   Tue Mar 21 17:06:47 2017 +0800

    BaseTools: Fix build failure for DynamicEx Pcd used in the Library
    
    Update DynExPcdTokenNumberMapping logic, currently even it is Library,
    its self's Pcd is saved into ModulePcdList.
    
    Fixes:https://bugzilla.tianocore.org/show_bug.cgi?id=434
    Cc: Liming Gao <liming.gao@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
    Reviewed-by: Liming Gao <liming.gao@intel.com>

commit c17956e0eedce299ac253ac40238ce90a5e623e0
Author: Derek Lin <derek.lin2@hpe.com>
Date:   Fri Feb 24 15:26:19 2017 +0800

    BaseTools: Skip module AutoGen by comparing timestamp.
    
    [Introduction]
    
    The BaseTool Build.py AutoGen parse INF meta-file and generate
    AutoGen.c/AutoGen.h/makefile. When we only change .c .h code, the
    AutoGen might be not necessary, but Build.py spend a lot of time on it.
    There's a -u flag to skip all module's AutoGen. In my environment, it save
    35%~50% of time in rebuild a ROM.
    However, if user change one .INF meta-file, then -u flag is not available.
    
    [Idea]
    
    AutoGen can compare meta-file's timestamp and decide if the module's
    AutoGen can be skipped. With this, when a module's INF is changed, we
    only run this module's AutoGen, we don't need to run other module's.
    
    [Implementation]
    
    In the end of a module's AutoGen, we create a AutoGenTimeStamp.
    The file save a file list that related to this module's AutoGen.
    In other word, the file list in AutoGenTimeStamp is INPUT files of
    module AutoGen, AutoGenTimeStamp file is OUTPUT.
    During rebuild, we compare time stamp between INPUT and OUTPUT, and
    decide if we can skip it.
    
    Below is the Input/Output of a module's AutoGen.
    
    [Input]
      1. All the DSC/DEC/FDF used by the platform.
      2. Macro and PCD defined by Build Options such as "build -D AAA=TRUE
         --pcd BbbPcd=0".
      3. INF file of a module.
      4. Source files of a module, list in [Sources] section of INF.
      5. All the library link by the module.
      6. All the .h files included by the module's sources.
    
    [Output]
      AutoGen.c/AutoGen.h/makefile/AutoGenTimeStamp
    
    [Testing]
    
    This patch save my build time. When I make a change without touching
    DSC/DEC/FDF, it is absolutely much faster than original rebuild,
    35%~50% time saving in my environment
    (compare to original tool rebuild time).
    If I change any DSC/DEC/FDF, there's no performance improve, because it
    can't skip any module's AutoGen.
    
    Please note that if your environment will generate DSC/FDF during prebuild,
    it will not skip any AutoGen because of DSC timestamp is changed. This will
    require prebuild script not to update metafile when content is not changed.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel