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

[Xen-devel] [libvirt test] 60641: regressions - trouble: broken/fail/pass

flight 60641 libvirt real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-libvirt-raw  3 host-install(3)         broken REGR. vs. 60629
 test-armhf-armhf-libvirt     11 guest-start               fail REGR. vs. 60629

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt-vhd  9 debian-di-install            fail   never pass
 test-armhf-armhf-libvirt-qcow2  9 debian-di-install            fail never pass
 test-amd64-i386-libvirt      12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-pair 21 guest-migrate/src_host/dst_host fail never 
 test-amd64-i386-libvirt-pair 21 guest-migrate/src_host/dst_host fail never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check 
fail never pass
 test-armhf-armhf-libvirt-xsm 12 migrate-support-check        fail   never pass
 test-armhf-armhf-libvirt-xsm 14 guest-saverestore            fail   never pass
 test-amd64-amd64-libvirt-qcow2 11 migrate-support-check        fail never pass
 test-amd64-amd64-libvirt-raw 11 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-qcow2 11 migrate-support-check        fail  never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check 
fail never pass
 test-amd64-amd64-libvirt-xsm 12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-xsm  12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-raw  11 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-vhd  11 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-vhd 11 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass

version targeted for testing:
 libvirt              f8fe8f03455783afcd62d79db7ce4120f514c629
baseline version:
 libvirt              82af954c527e88111b05d50953b80eb4afde4d9a

Last test of basis    60629  2015-08-07 21:19:27 Z    2 days
Testing same since    60641  2015-08-09 09:09:00 Z    1 days    1 attempts

People who touched revisions under test:
  Laine Stump <laine@xxxxxxxxx>

 build-amd64-xsm                                              pass    
 build-armhf-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-armhf-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm           pass    
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm            pass    
 test-amd64-amd64-libvirt-xsm                                 pass    
 test-armhf-armhf-libvirt-xsm                                 fail    
 test-amd64-i386-libvirt-xsm                                  pass    
 test-amd64-amd64-libvirt                                     pass    
 test-armhf-armhf-libvirt                                     fail    
 test-amd64-i386-libvirt                                      pass    
 test-amd64-amd64-libvirt-pair                                fail    
 test-amd64-i386-libvirt-pair                                 fail    
 test-amd64-amd64-libvirt-qcow2                               pass    
 test-armhf-armhf-libvirt-qcow2                               fail    
 test-amd64-i386-libvirt-qcow2                                pass    
 test-amd64-amd64-libvirt-raw                                 pass    
 test-armhf-armhf-libvirt-raw                                 broken  
 test-amd64-i386-libvirt-raw                                  pass    
 test-amd64-amd64-libvirt-vhd                                 pass    
 test-armhf-armhf-libvirt-vhd                                 fail    
 test-amd64-i386-libvirt-vhd                                  pass    

sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at

Explanation of these reports, and of osstest in general, is at

Test harness code can be found at

broken-step test-armhf-armhf-libvirt-raw host-install(3)

Not pushing.

commit f8fe8f03455783afcd62d79db7ce4120f514c629
Author: Laine Stump <laine@xxxxxxxxx>
Date:   Wed Jul 22 11:59:00 2015 -0400

    conf: more useful error message when pci function is out of range
    If a pci address had a function number out of range, the error message
    would be:
      Insufficient specification for PCI address
    which is logged by virDevicePCIAddressParseXML() after
    virDevicePCIAddressIsValid returns a failure.
    This patch enhances virDevicePCIAddressIsValid() to optionally report
    the error itself (since it is the place that decides which part of the
    address is "invalid"), and uses that feature when calling from
    virDevicePCIAddressParseXML(), so that the error will be more useful,
      Invalid PCI address function=0x8, must be <= 7
    Previously, virDevicePCIAddressIsValid didn't check for the
    theoretical limits of domain or bus, only for slot or function. While
    adding log messages, we also correct that ommission. (The RNG for PCI
    addresses already enforces this limit, which by the way means that we
    can't add any negative tests for this - as far as I know our
    domainschematest has no provisions for passing XML that is supposed to
    Note that virDevicePCIAddressIsValid() can only check against the
    absolute maximum attribute values for *any* possible PCI controller,
    not for the actual maximums of the specific controller that this
    device is attaching to; fortunately there is later more specific
    validation for guest-side PCI addresses when building the set of
    assigned PCI addresses. For host-side PCI addresses (e.g. for
    <hostdev> and for network device pools), we rely on the error that
    will be logged when it is found that the device doesn't actually
    This resolves:

Xen-devel mailing list



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