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

[Xen-devel] [ovmf baseline-only test] 75558: tolerable FAIL

This run is configured for baseline tests only.

flight 75558 ovmf real [real]

Failures :-/ but no regressions.

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

version targeted for testing:
 ovmf                 d3d97b378fe4d0bfbcbdb296d06bcf1d09165480
baseline version:
 ovmf                 fd950156738ce878c0ba29af99da2ffcac5168e1

Last test of basis    75556  2018-11-01 09:00:43 Z    0 days
Testing same since    75558  2018-11-01 14:32:17 Z    0 days    1 attempts

People who touched revisions under test:
  Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
  Tomas Pilar <tpilar@xxxxxxxxxxxxxx>
  Zhiju.Fan <zhijux.fan@xxxxxxxxx>
  zhijufan <zhijux.fan@xxxxxxxxx>

 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          fail    
 build-i386-libvirt                                           fail    
 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

Test harness code can be found at

Push not applicable.

commit d3d97b378fe4d0bfbcbdb296d06bcf1d09165480
Author: zhijufan <zhijux.fan@xxxxxxxxx>
Date:   Wed Oct 17 13:57:01 2018 +0800

    BaseTools: Add special handle for '\' use in Pcd Value
    V2: Follow PEP8 to not multiples import on one line
    Fixes: https://bugzilla.tianocore.org/show_bug.cgi?id=1287
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Zhiju.Fan <zhijux.fan@xxxxxxxxx>
    Reviewed-by: Jaben Carsey <jaben.carsey@xxxxxxxxx>

commit 5b9639e697350c9e18e98ddb0119e8598b004a8f
Author: Tomas Pilar <tpilar@xxxxxxxxxxxxxx>
Date:   Tue Oct 30 00:52:53 2018 +0800

    BaseTools: Fix merge in FDF parser for OptionROM override
    Cc: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Tomas Pilar <tpilar@xxxxxxxxxxxxxx>
    Reviewed-by: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>

commit bfc87aa78e77ed15b09d1b4499c5eab63e8842bb
Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
Date:   Mon Oct 22 17:03:07 2018 +0800

    MdeModulePkg/PiSmmIpl: Do not reset SMRAM to UC when CPU driver runs
    Today's PiSmmIpl implementation initially sets SMRAM to WB to speed
    up the SMM core/modules loading before SMM CPU driver runs.
    When SMM CPU driver runs, PiSmmIpl resets the SMRAM to UC. It's done
    in SmmIplDxeDispatchEventNotify(). COMM_BUFFER_SMM_DISPATCH_RESTART
    is returned from SMM core that SMM CPU driver is just dispatched.
    Since now the SMRR is widely used to control the SMRAM cache setting.
    It's not needed to reset the SMRAM to UC anymore.
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx>

Xen-devel mailing list



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