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

[libvirt test] 60708: regressions - FAIL



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

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-libvirt           5 libvirt-build             fail REGR. vs. 60681
 build-i386-libvirt            5 libvirt-build             fail REGR. vs. 60681
 build-armhf-libvirt           5 libvirt-build             fail REGR. vs. 60681

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt-vhd  1 build-check(1)               blocked  n/a
 test-armhf-armhf-libvirt-qcow2  1 build-check(1)               blocked  n/a
 test-amd64-amd64-libvirt      1 build-check(1)               blocked  n/a
 test-amd64-i386-libvirt-pair  1 build-check(1)               blocked  n/a
 test-armhf-armhf-libvirt      1 build-check(1)               blocked  n/a
 test-armhf-armhf-libvirt-xsm  1 build-check(1)               blocked  n/a
 test-amd64-i386-libvirt-qcow2  1 build-check(1)               blocked  n/a
 test-amd64-amd64-libvirt-qcow2  1 build-check(1)               blocked  n/a
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a
 test-amd64-amd64-libvirt-raw  1 build-check(1)               blocked  n/a
 test-amd64-amd64-libvirt-pair  1 build-check(1)               blocked  n/a
 test-amd64-i386-libvirt-raw   1 build-check(1)               blocked  n/a
 test-amd64-i386-libvirt-vhd   1 build-check(1)               blocked  n/a
 test-amd64-i386-libvirt       1 build-check(1)               blocked  n/a
 test-amd64-amd64-libvirt-xsm  1 build-check(1)               blocked  n/a
 test-amd64-i386-libvirt-xsm   1 build-check(1)               blocked  n/a
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a
 test-amd64-amd64-libvirt-vhd  1 build-check(1)               blocked  n/a
 test-armhf-armhf-libvirt-raw  1 build-check(1)               blocked  n/a

version targeted for testing:
 libvirt              834c5720e4434f0bcc807bb1cf20855af63e24a3
baseline version:
 libvirt              1b08cc170a84077afd4d15f4639a9a2cf398e9a2

Last test of basis    60681  2015-08-13 01:48:19 Z    3 days
Testing same since    60708  2015-08-15 09:04:13 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Erik Skultety <eskultet@xxxxxxxxxx>
  Guido Günther <agx@xxxxxxxxxxx>
  John Ferlan <jferlan@xxxxxxxxxx>
  Martin Kletzander <mkletzan@xxxxxxxxxx>
  Michal Privoznik <mprivozn@xxxxxxxxxx>
  Tomas Meszaros <exo@xxxxxx>

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                                          fail
 build-armhf-libvirt                                          fail
 build-i386-libvirt                                           fail
 build-amd64-pvops                                            pass
 build-armhf-pvops                                            pass
 build-i386-pvops                                             pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm           blocked
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm            blocked
 test-amd64-amd64-libvirt-xsm                                 blocked
 test-armhf-armhf-libvirt-xsm                                 blocked
 test-amd64-i386-libvirt-xsm                                  blocked
 test-amd64-amd64-libvirt                                     blocked
 test-armhf-armhf-libvirt                                     blocked
 test-amd64-i386-libvirt                                      blocked
 test-amd64-amd64-libvirt-pair                                blocked
 test-amd64-i386-libvirt-pair                                 blocked
 test-amd64-amd64-libvirt-qcow2                               blocked
 test-armhf-armhf-libvirt-qcow2                               blocked
 test-amd64-i386-libvirt-qcow2                                blocked
 test-amd64-amd64-libvirt-raw                                 blocked
 test-armhf-armhf-libvirt-raw                                 blocked
 test-amd64-i386-libvirt-raw                                  blocked
 test-amd64-amd64-libvirt-vhd                                 blocked
 test-armhf-armhf-libvirt-vhd                                 blocked
 test-amd64-i386-libvirt-vhd                                  blocked


------------------------------------------------------------
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 834c5720e4434f0bcc807bb1cf20855af63e24a3
Author: Erik Skultety <eskultet@xxxxxxxxxx>
Date:   Mon Jun 15 18:53:58 2015 +0200

    tools: Introduce new client generic module vsh

    In order to share as much virsh' logic as possible with upcomming
    virt-admin client we need to split virsh logic into virsh specific and
    client generic features.

    Since majority of virsh methods should be generic enough to be used by
    other clients, it's much easier to rename virsh specific data to virshX
    than doing this vice versa. It moved generic virsh commands (including info
    and opts structures) to generic module vsh.c.

    Besides renaming methods and structures, this patch also involves 
introduction
    of a client specific control structure being referenced as private data in 
the
    original control structure, introduction of a new global vsh Initializer,
    which currently doesn't do much, but there is a potential for added
    functionality in the future.
    Lastly it introduced client hooks which are especially necessary during
    client connecting phase.

commit b5d63e997bb4cbaa3c9d5e35e38998b0c1e78fd1
Author: Tomas Meszaros <exo@xxxxxx>
Date:   Mon Aug 10 21:59:18 2015 +0200

    qemu: Implement virDomainRename

    Currently supports only renaming inactive domains without snapshots.

    Signed-off-by: Tomas Meszaros <exo@xxxxxx>
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 9877d8406cd32864278dfa7bb040c542782d4cfb
Author: Tomas Meszaros <exo@xxxxxx>
Date:   Mon Aug 10 21:59:17 2015 +0200

    Introduce new VIR_DOMAIN_EVENT_DEFINED_RENAMED event

    This should be emitted whenever a domain is renamed.

    Signed-off-by: Tomas Meszaros <exo@xxxxxx>

commit 28257dc2bee84f386c51f647a1824789e3b11862
Author: Tomas Meszaros <exo@xxxxxx>
Date:   Mon Aug 10 21:59:16 2015 +0200

    domain_conf: Introducde virDomainObjListRenameAddNew() & 
virDomainObjListRenameRemove()

    We just need to update the entry in the second hash table. Since commit 
8728a56
    we have two hash tables for the domain list so that we can do O(1) lookup
    regardless of looking up by UUID or name. Since with renaming a domain UUID 
does
    not change, we only need to update the second hash table, where domains are
    referenced by their name.

    We will call both functions from the qemuDomainRename().

    Signed-off-by: Tomas Meszaros <exo@xxxxxx>

commit ff486e0d29a7c08e7131447ca3c878ed791def4e
Author: Tomas Meszaros <exo@xxxxxx>
Date:   Mon Aug 10 21:59:15 2015 +0200

    virsh: Implement "domrename" command

    This patch implements new virsh command, domrename.

    Using domrename, it will be possible to rename domain from the virsh shell 
by
    calling virRenameDomain API.

    It takes two arguments, current domain name and new domain name.

    Example:

    virsh # list --all
     Id    Name                           State
     ----------------------------------------------------
      -     bar                            shut off

    virsh # domrename bar foo
    Domain successfully renamed

    virsh # list --all
     Id    Name                           State
     ----------------------------------------------------
      -     foo                            shut off

    virsh #

    Signed-off-by: Tomas Meszaros <exo@xxxxxx>

commit 9f7a559a6d1ab4103de238d59910baefa7b425ff
Author: Tomas Meszaros <exo@xxxxxx>
Date:   Mon Aug 10 21:59:14 2015 +0200

    Introduce virDomainRename API

    Also, among with this new API new ACL that restricts rename
    capability is invented too.

    Signed-off-by: Tomas Meszaros <exo@xxxxxx>
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 0e4972fe48aeaade393daf089013092a2ecde4b3
Author: Guido Günther <agx@xxxxxxxxxxx>
Date:   Thu Aug 13 12:20:29 2015 +0200

    Detect location of qemu-bridge-helper

    RedHat and Debian based distros use different locations

    Reference: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790935

commit 151ba022939dad1e562c4156cb62e7a3ade6a7f5
Author: Guido Günther <agx@xxxxxxxxxxx>
Date:   Thu Aug 13 14:19:50 2015 +0200

    Check if qemu-bridge-helper exists and is executable

    Otherwise the error is just

        error: Failed to create domain from test1.xml
        error: failed to retrieve file descriptor for interface: Transport 
endpoint is not connected

    since we don't get a sensible error after the fork.

commit 11d571470a059421755aa014b0560e7f3b2fea9d
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Fri Jun 19 15:03:50 2015 -0400

    conf: Remove 'vmdef' from virDomainHostdevDefParseXML

    Since it's not used, let's remove it to avoid any future usage.

    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>

commit 776924e37649f2d47acd805746d5fd9325212ea5
Author: Martin Kletzander <mkletzan@xxxxxxxxxx>
Date:   Sun Jul 26 18:49:02 2015 +0200

    qemu: Use numad information when getting pin information

    Pinning information returned for emulatorpin and vcpupin calls is being
    returned from our data without querying cgroups for some time.  However,
    not all the data were utilized.  When automatic placement is used the
    information is not returned for the calls mentioned above.  Since the
    numad hint in private data is properly saved/restored, we can safely use
    it to return true information.

    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1162947

    Signed-off-by: Martin Kletzander <mkletzan@xxxxxxxxxx>

commit 8ce86722d78d8b2a1e7d9cb29571beb791c9f3d7
Author: Martin Kletzander <mkletzan@xxxxxxxxxx>
Date:   Fri Jul 24 16:06:33 2015 +0200

    qemu: Keep numad hint after daemon restart

    The numad hint stored in priv->autoNodeset is information that gets lost
    during daemon restart.  And because we would like to use that
    information in the future, we also need to save it in the status XML.
    For the sake of tests, we need to initialize nnumaCell_max to some
    value, so that the restoration doesn't fail in our test suite.  There is
    no need to fill in the actual numa cell data since the recalculating
    function virCapabilitiesGetCpusForNodemask() will not fail, it will just
    skip filling the data in the bitmap which we don't use in tests anyway.

    Signed-off-by: Martin Kletzander <mkletzan@xxxxxxxxxx>

commit 7c8028cda95c3af388f7485e682ed07629bb9e7a
Author: Martin Kletzander <mkletzan@xxxxxxxxxx>
Date:   Fri Jul 24 19:35:00 2015 +0200

    conf: Pass private data to Parse function of XML options

    This needs a reorder of XML option definitions.  It might come in handy
    one day.

    Signed-off-by: Martin Kletzander <mkletzan@xxxxxxxxxx>

commit 92ddffdbd3c91d99f8f7ed9b661388a2c5d36cc2
Author: Martin Kletzander <mkletzan@xxxxxxxxxx>
Date:   Thu Aug 13 10:03:12 2015 +0200

    qemu: Fix segfault when parsing private domain data

    When parsing private domain data, there are two paths that are flawed.
    They are both error paths, just from different parts of the function.
    One of them can call free() on an uninitialized pointer.  Initialization
    to NULL is enough here.  The other one is a bit trickier to explain, but
    as easy as the first one to fix.  We create capabilities, parse them and
    then assign them into the private data pointer inside the domain object.
    If, however, we get to fail from now on, the error path calls unrefs the
    capabilities and then, when the domain object is being cleaned,
    qemuDomainObjPrivateFree() tries to unref them as well.  That causes a
    segfault.  Settin the pointer to NULL upon successful addition to the
    private data is enough.

    Signed-off-by: Martin Kletzander <mkletzan@xxxxxxxxxx>

_______________________________________________
Osstest-output mailing list
Osstest-output@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/osstest-output

 


Rackspace

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