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

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



This run is configured for baseline tests only.

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

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 75123
 test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install      fail like 75123

version targeted for testing:
 ovmf                 983f5abb9a0d6cf9cfb5e16d671f15e5dc7510d8
baseline version:
 ovmf                 6861765935d5b69803321ba6e43240845c7ab0e5

Last test of basis    75123  2018-08-25 19:21:23 Z    2 days
Testing same since    75130  2018-08-27 12:55:15 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ruiyu Ni <ruiyu.ni@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 983f5abb9a0d6cf9cfb5e16d671f15e5dc7510d8
Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
Date:   Thu Aug 23 10:50:16 2018 +0800

    MdeModulePkg/PciBus: Restrict one VGA per HostBridge not Segment
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1109
    
    Today's restriction of VGA device is to have only one VGA device
    enabled per PCI segment. It's not correct because several segments
    may share one IO / MMIO address space.
    We should restrict to have one VGA per Host Bridge because each
    Host Bridge has its only IO / MMIO address space.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

commit 06da1e310bcea971073a8dabc5c3d35bc190847c
Author: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
Date:   Thu Aug 23 10:34:33 2018 +0800

    MdeModulePkg/PciBus: Refine ActiveVGADeviceOnTheRootBridge
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1109
    The patch doesn't change any behavior of this function.
    It just renames the function to LocateVgaDevice() and renames
    some parameters and local variables.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Reviewed-by: Star Zeng <star.zeng@xxxxxxxxx>

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

 


Rackspace

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