[ovmf baseline-only test] 67997: trouble: broken/pass

[ovmf baseline-only test] 67997: trouble: broken/pass

[Platform Team regression test user]

This run is configured for baseline tests only.

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

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-ovmf-amd64  3 host-install(3) broken REGR. vs. 67994

version targeted for testing:
 ovmf                 669b6cc60bf610bbee32e79ed165ca604764c169
baseline version:
 ovmf                 5f609eb837f235e28464285a2fb768e39cd51b56

Last test of basis    67994  2016-11-04 08:18:04 Z    0 days
Testing same since    67997  2016-11-04 16:17:17 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Bell Song <binx.song@intel.com>
  Dandan Bi <dandan.bi@intel.com>
  Song, BinX <binx.song@intel.com>
  Yonghong Zhu <yonghong.zhu@intel.com>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         broken  
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    


------------------------------------------------------------
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 test-amd64-amd64-xl-qemuu-ovmf-amd64 host-install(3)

Push not applicable.

------------------------------------------------------------
commit 669b6cc60bf610bbee32e79ed165ca604764c169
Author: Yonghong Zhu <yonghong.zhu@intel.com>
Date:   Thu Nov 3 15:44:17 2016 +0800

    BaseTools: Fix the Windows GCC Build Failure with too long path
    
    When path is too long, build tool will wrap them into resp.txt, then call
    gcc @resp.txt. It will cause windows GCC build failure, because resp.txt
    still uses windows directory separator \. This patch change the \ to /.
    
    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 0c45a5b288437f62b93c046b4cc8827919a79fd1
Author: Song, BinX <binx.song@intel.com>
Date:   Thu Nov 3 10:33:20 2016 +0800

    MdePkg/BaseLib: Move CHAR_NULL definition to Base.h in BaseLib
    
    - Required unicode control chars -> Null character
    - Remove CHAR_NULL definition in SimpleTextIn.h
    - https://bugzilla.tianocore.org/show_bug.cgi?id=172
    
    Cc: Liming Gao <liming.gao@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Bell Song <binx.song@intel.com>
    Reviewed-by: Liming Gao <liming.gao@intel.com>

commit e135e4a79efdcc1de76a5a38bb17d9f925e6f5a1
Author: Dandan Bi <dandan.bi@intel.com>
Date:   Fri Oct 28 09:34:51 2016 +0800

    IntelFrameworkModulePkg/BootMaint: Show "Change Boot order" page correctly
    
    Some boot options may be deleted in the "Delete Boot Option page",
    But the data BootOptionOrder in BmmFakeNvData may not be updated.
    So when user enter the "Change Boot Order" page, we should not always
    get the BootOptionOrder in BmmFakeNvData, it will result in incorrect
    UI behaviors. When the Boot Options have been saved,
    we should get the BootOptionOrder through function GetBootOrder.
    
    For driver option codes need to do the same change.
    
    This patch is to fix the issue in bugzilla:
    https://bugzilla.tianocore.org/show_bug.cgi?id=39
    
    Cc: Eric Dong <eric.dong@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Dandan Bi <dandan.bi@intel.com>
    Reviewed-by: Eric Dong <eric.dong@intel.com>

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