[Xen-devel] [libvirt test] 82637: regressions - FAIL

[osstest service owner <osstest-admin@xxxxxxxxxxxxxx>]

flight 82637 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82637/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-libvirt-xsm  6 xen-boot                  fail REGR. vs. 82511

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt     14 guest-saverestore            fail   never pass
 test-armhf-armhf-libvirt     12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-xsm 12 migrate-support-check        fail   never pass
 test-armhf-armhf-libvirt-qcow2 11 migrate-support-check        fail never pass
 test-armhf-armhf-libvirt-qcow2 13 guest-saverestore            fail never pass
 test-amd64-i386-libvirt      12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-xsm  12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check 
fail never pass
 test-amd64-amd64-libvirt-vhd 11 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check 
fail never pass
 test-armhf-armhf-libvirt-raw 13 guest-saverestore            fail   never pass
 test-armhf-armhf-libvirt-raw 11 migrate-support-check        fail   never pass

version targeted for testing:
 libvirt              9cb8b0e5a4650e3d22c21b100970686b7da587b8
baseline version:
 libvirt              98782f88991a390a358cea960b5776f72fc14451

Last test of basis    82511  2016-02-14 13:33:09 Z    1 days
Testing same since    82637  2016-02-15 07:01:16 Z    0 days    1 attempts

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

jobs:
 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                                pass    
 test-amd64-i386-libvirt-pair                                 pass    
 test-armhf-armhf-libvirt-qcow2                               fail    
 test-armhf-armhf-libvirt-raw                                 fail    
 test-amd64-amd64-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
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

Test harness code can be found at
    http://xenbits.xen.org/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
commit 9cb8b0e5a4650e3d22c21b100970686b7da587b8
Author: Laine Stump <laine@xxxxxxxxx>
Date:   Thu Feb 11 15:24:17 2016 -0500

    util: clean up and expand 802.1QbX negotiation logging
    
    The existing log messages for this have several problems; there are
    two lines of log when one will suffice, they duplicate the function
    name in log message (when it's already included by VIR_DEBUG), they're
    missing some useful bits, they get logged even when the call is a NOP.
    
    This patch cleans up the problems with those existing logs, and also
    adds a new VIR_INFO-level log down at the function that is actually
    creating and sending the netlink message that logs *everything* going
    into the netlink message (which turns out to be much more useful in
    practice for me; I didn't want to eliminate the logs at the existing
    location though, in case they are useful in some scenario I'm
    unfamiliar with; anyway those logs are remaining at debug level, so it
    shouldn't be a bother to anyone).

commit eb72bd63c15817b1b74f0528f86bfe3c8da2bc2c
Author: Laine Stump <laine@xxxxxxxxx>
Date:   Tue Feb 9 12:28:48 2016 -0500

    network: consolidated info log for all network allocate/free operations
    
    There are three functions that deal with allocating and freeing
    devices from a networks netdev/pci device pool:
    network(Allocate|Notify|Release)ActualDevice(). These functions also
    maintain a counter of the number of domains currently using a network
    (regardless of whether or not that network uses a device pool). Each
    of these functions had multiple log messages (output using VIR_DEBUG)
    that were in slightly different formats and gave varying amounts of
    information.
    
    This patch creates a single function to log the pertinent information
    in a consistent manner for all three of these functions. Along with
    assuring that all the functions produce a consistent form of output
    (and making it simpler to change), it adds the MAC address of the
    domain interface involved in the operation, making it possible to
    verify which interface of which domain the operation is being done for
    (assuming that all MAC addresses are unique, of course).
    
    All of these messages are raised from DEBUG to INFO, since they don't
    happen that often (once per interface per domain/libvirtd start or
    domain stop), and can be very informative and helpful - eliminating
    the need to log debug level messages makes it much easier to sort
    these out.

commit 3ea8b8b87f5c9efdf12b2a162cac072081355f63
Author: Laine Stump <laine@xxxxxxxxx>
Date:   Thu Feb 11 13:52:04 2016 -0500

    network: consolidate connection count updates for device pool
    
    networkReleaseActualDevice() and networkNotifyActualDevice() both were
    updating the individual devices' connections count in two separate
    places (unlike networkAllocateActualDevice() which does it in a single
    unified place after success:). The code is correct, but prone to
    confusion / later breakage. All of these updates are anyway located at
    the end of if/else clauses that are (with the exception of a single
    VIR_DEBUG() in each case) immediately followed by the success: label
    anyway, so this patch replaces the duplicated ++/-- instructions with
    a single ++/-- inside a qualifying "if (dev)" down below success:.
    (NB: if dev != NULL, by definition we are using a device (either pci
    or netdev, doesn't matter for these purposes) from the network's pool)
    
    The VIR_DEBUG args (which will be replaced in a followup patch anyway)
    were all adjusted to account for the connection count being out of
    date at the time.

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