[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ovmf baseline-only test] 75001: tolerable FAIL



This run is configured for baseline tests only.

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

Failures :-/ but no regressions.

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install     fail like 74999
 test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install      fail like 74999

version targeted for testing:
 ovmf                 5b73e17fb17c6935d894b0084f32421e717c247f
baseline version:
 ovmf                 005c855dc6be0f61f76de0d7ec4a62ee737518d6

Last test of basis    74999  2018-07-24 05:19:57 Z    0 days
Testing same since    75001  2018-07-24 14:52:20 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
  Yunhua Feng <yunhuax.feng@xxxxxxxxx>

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                         fail    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          fail    


------------------------------------------------------------
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


Push not applicable.

------------------------------------------------------------
commit 5b73e17fb17c6935d894b0084f32421e717c247f
Author: Yunhua Feng <yunhuax.feng@xxxxxxxxx>
Date:   Fri Jul 20 15:51:39 2018 +0800

    BaseTools: Fix the different token with the same PCD
    
    If the different token with the same PCD names are used in the driver,
    build can pass. If the different token with the same PCD name are used
    in the different library, then the driver build will fail. The reason
    is that the driver autogen.c is not generated correctly for the second
    case. BaseTools should check the duplicated PCD name is the driver and
    its linked libraries.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Yunhua Feng <yunhuax.feng@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit bfa7eeb61d94623ddbe43b916a0bb1dc0f73a292
Author: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
Date:   Mon Jul 23 11:58:22 2018 +0800

    BaseTools: Correct _PCD_PATCHABLE_TokenName_SIZE's value
    
    current if user use PatchPcdSetPtr in library, it will report the
    _PCD_PATCHABLE_TokenName_SIZE is not defined.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

_______________________________________________
osstest-output mailing list
osstest-output@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/osstest-output

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.