This run is configured for baseline tests only.

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

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

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                   2 hosts-allocate        broken baseline untested
 build-amd64-pvops             2 hosts-allocate        broken baseline untested
 build-amd64-xsm               2 hosts-allocate        broken baseline untested
 build-i386-pvops              2 hosts-allocate        broken baseline untested
 build-i386-xsm                2 hosts-allocate        broken baseline untested
 build-i386                    2 hosts-allocate        broken baseline untested
 build-amd64-xsm               3 capture-logs          broken baseline untested
 build-amd64                   3 capture-logs          broken baseline untested
 build-i386                    3 capture-logs          broken baseline untested
 build-amd64-pvops             3 capture-logs          broken baseline untested
 build-i386-xsm                3 capture-logs          broken baseline untested
 build-i386-pvops              3 capture-logs          broken baseline untested

version targeted for testing:
 ovmf                 153f5c7a93be09403891404c06e5b0e24eb019a3
baseline version:
 ovmf                 8b0e67821bd66af70433ee4bb858325f3033609a

Last test of basis    74580  2018-04-12 00:49:45 Z    1 days
Testing same since    74584  2018-04-13 00:27:52 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Feng, YunhuaX </o=Intel/ou=Exchange Administrative Group 
(FYDIBOHF23SPDLT)/cn=Recipients/cn=Feng, YunhuaX4e1>
  Kinney, Michael D <michael.d.kin...@intel.com>
  Michael D Kinney <michael.d.kin...@intel.com>
  Yunhua Feng <yunhuax.f...@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-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-amd64 hosts-allocate
broken-step build-amd64-pvops hosts-allocate
broken-step build-amd64-xsm hosts-allocate
broken-step build-i386-pvops hosts-allocate
broken-step build-i386-xsm hosts-allocate
broken-step build-i386 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 153f5c7a93be09403891404c06e5b0e24eb019a3
Author: Kinney, Michael D <michael.d.kin...@intel.com>
Date:   Mon Apr 9 15:47:19 2018 -0700

    SignedCapsulePkg/SystemFirmwareReportDxe: Pass thru on same handle
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=928
    
    Use HandleProtocol() to pass thru a SetImage() call to the
    System FMP Protocol that must be on the same handle as the
    FMP Protocol.
    
    Cc: Jiewen Yao <jiewen....@intel.com>
    Signed-off-by: Michael D Kinney <michael.d.kin...@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Reviewed-by: Jiewen Yao <jiewen....@intel.com>

commit d69d9227d046211265de1fab5580c50a65944614
Author: Kinney, Michael D <michael.d.kin...@intel.com>
Date:   Sat Mar 31 10:17:29 2018 -0700

    SignedCapsulePkg/SystemFirmwareUpdateDxe: Single FMP
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=928
    
    Uninstall all System FMP Protocols for the current FW device.
    
    If an FMP Protocol for the current FW device is already present,
    then install the new System FMP protocol onto the same handle as
    the FMP Protocol.  Otherwise, install the FMP protocol onto a
    new handle.
    
    This supports use cases where multiple capsules for the
    same system firmware device are processed on the same
    boot of the platform.  It guarantees there is at most one
    FMP protocol for each system firmware device.
    
    Cc: Jiewen Yao <jiewen....@intel.com>
    Signed-off-by: Michael D Kinney <michael.d.kin...@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Reviewed-by: Jiewen Yao <jiewen....@intel.com>

commit a146c532c754106431b063fec9985a838afd82be
Author: Feng, YunhuaX </o=Intel/ou=Exchange Administrative Group 
(FYDIBOHF23SPDLT)/cn=Recipients/cn=Feng, YunhuaX4e1>
Date:   Tue Apr 10 09:12:49 2018 +0800

    BaseTools: fix --genfds-multi-thread generate makefile issue
    
    1. when inf file is binary module, not generate makefile,
      so need generate ffs with previous method.
    2. generate Ui section maybe override and the string is not
      $(MODULE_NAME)
      like as:
      INF  RuleOverride = UI MdeModulePkg/Application/UiApp/UiApp.inf
    3. Trim generate incorrect Offset.raw when some vfr not generate .lst
       file in Debug directory, Trim get the VFR name with the .c files
       replacement.
    4. fix some depex file not generate issue
    
    Cc: Liming Gao <liming....@intel.com>
    Cc: Yonghong Zhu <yonghong....@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Yunhua Feng <yunhuax.f...@intel.com>
    Reviewed-by: Yonghong Zhu <yonghong....@intel.com>

commit 9a8d7aa7f796ce68ece2815d268889ac4e2ac318
Author: Feng, YunhuaX </o=Intel/ou=Exchange Administrative Group 
(FYDIBOHF23SPDLT)/cn=Recipients/cn=Feng, YunhuaX4e1>
Date:   Tue Apr 10 09:10:41 2018 +0800

    BaseTools: argument genfds-multi-thread create GenSec command issue
    
    Issue:
      genfds-multi-thread create makefile before section file generation,
      so it get alignment is zero from empty file. It is incorrect.
    solution:
      GenSec get section alignment from input file when the input alignment
      is zero.
    
    Cc: Liming Gao <liming....@intel.com>
    Cc: Yonghong Zhu <yonghong....@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Yunhua Feng <yunhuax.f...@intel.com>
    Reviewed-by: Yonghong Zhu <yonghong....@intel.com>

commit 6ecab5ad077ea34467ff29ea1f5b77fa5c1e3447
Author: Feng, YunhuaX </o=Intel/ou=Exchange Administrative Group 
(FYDIBOHF23SPDLT)/cn=Recipients/cn=Feng, YunhuaX4e1>
Date:   Tue Apr 10 09:09:45 2018 +0800

    BaseTools: Correct GenSec argument dummy free memory issue
    
    Free DummyFileBuffer and set DummyFileBuffer to NULL.
    
    Cc: Liming Gao <liming....@intel.com>
    Cc: Yonghong Zhu <yonghong....@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Yunhua Feng <yunhuax.f...@intel.com>
    Reviewed-by: Yonghong Zhu <yonghong....@intel.com>

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

Reply via email to