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

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



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

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-i386-libvirt       3 host-install(3)         broken REGR. vs. 58510

Regressions which are regarded as allowable (not blocking):
 test-amd64-i386-libvirt-xsm  11 guest-start                  fail   like 58510
 test-armhf-armhf-libvirt     11 guest-start                  fail   like 58510

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt-xsm 11 guest-start                  fail   never pass
 test-amd64-amd64-libvirt-xsm 12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass

version targeted for testing:
 libvirt              ecb9a7a10b1559ddb41832f75d012054c1017366
baseline version:
 libvirt              bcf1349bb180d2a3aab6906aea524e2d6aa7e52a

------------------------------------------------------------
People who touched revisions under test:
  Boris Fiuczynski <fiuczy@xxxxxxxxxxxxxxxxxx>
  Guido Günther <agx@xxxxxxxxxxx>
  John Ferlan <jferlan@xxxxxxxxxx>
  Ján Tomko <jtomko@xxxxxxxxxx>
  Martin Kletzander <mkletzan@xxxxxxxxxx>
  Michal Privoznik <mprivozn@xxxxxxxxxx>
  Peter Krempa <pkrempa@xxxxxxxxxx>
------------------------------------------------------------

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-xsm                                 pass
 test-armhf-armhf-libvirt-xsm                                 fail
 test-amd64-i386-libvirt-xsm                                  fail
 test-amd64-amd64-libvirt                                     pass
 test-armhf-armhf-libvirt                                     fail
 test-amd64-i386-libvirt                                      broken


------------------------------------------------------------
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

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

broken-step test-amd64-i386-libvirt host-install(3)

Not pushing.

------------------------------------------------------------
commit ecb9a7a10b1559ddb41832f75d012054c1017366
Author: Guido Günther <agx@xxxxxxxxxxx>
Date:   Fri Jun 5 12:41:22 2015 +0200

    configure: Remove check for pkcheck_supports_uid

    We're using Polkit's DBus API so no need to check wether this feature is
    supported. We don't use the result or the path to the pkcheck program
    anywhere.

commit 38788a3209c5d7d2cece261ae128fb07bb348ce7
Author: Martin Kletzander <mkletzan@xxxxxxxxxx>
Date:   Mon Jun 15 10:41:17 2015 +0200

    tests: Use libvirt properly with initialization and error dispatching

    We were using "complicated" error printing in virnetservertest even
    though we could've just dispatched the error.  Also add some good
    practices that might come in handy (the code may fail without proper
    initialization and event loop).

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

commit 73ad20e936b0fc9fac59efb66e6f77a5739aab4b
Author: Martin Kletzander <mkletzan@xxxxxxxxxx>
Date:   Mon Jun 15 11:28:11 2015 +0200

    Generate JSON with mDNS entries only when built --with-avahi

    One string was already used only if that condition was true, second one
    is added now.  Both are used in a nicer way.

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

commit fcc2aab688244d3e07c578080653ee526c056b38
Author: Martin Kletzander <mkletzan@xxxxxxxxxx>
Date:   Thu Jun 11 13:58:43 2015 +0200

    rpc: Fix possible crash when MDNSAddEntry fails

    If virNetServerMDNSAddEntry() fails when adding a service to a server,
    it doesn't decrease the number of services.  Hence access to their
    members segfaults (e.g. when free()-ing the sruct).

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

commit 5e55534b9ab4e1c09085e67e20f46780d1132e27
Author: Martin Kletzander <mkletzan@xxxxxxxxxx>
Date:   Thu May 21 16:39:26 2015 -0700

    build: Remove unnecessarily repeated rules for syms -> def

    Suggested-by: Michal Prívozník <mprivozn@xxxxxxxxxx>
    Signed-off-by: Martin Kletzander <mkletzan@xxxxxxxxxx>

commit 840eca32aba4f67e3d4473aae5b075062bc49006
Author: Boris Fiuczynski <fiuczy@xxxxxxxxxxxxxxxxxx>
Date:   Wed Jun 10 09:02:36 2015 +0200

    qemu: monitor: Add memory balloon support for virtio-ccw

    The search for the memory balloon driver object is extended by a
    second known name "virtio-balloon-ccw" in support for virtio-ccw.

    Signed-off-by: Boris Fiuczynski <fiuczy@xxxxxxxxxxxxxxxxxx>
    Reviewed-by: Daniel Hansel <daniel.hansel@xxxxxxxxxxxxxxxxxx>
    Reviewed-by: Eric Farman <farman@xxxxxxxxxxxxxxxxxx>
    Reviewed-by: Stefan Zimmermann <stzi@xxxxxxxxxxxxxxxxxx>

commit 17ba622451d51bbe7b0000bab0172894b8e60ae8
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Mon Jun 15 14:08:05 2015 +0200

    man: clarify usage of virsh blockcopy with --xml

    The --xml option is mandatory if an XML description is used.
    Otherwise the third parameter is treated as the destination.

    https://bugzilla.redhat.com/show_bug.cgi?id=1206406#c3

commit 4ed2b9a7e4bf2109b3711e493e6c4559d7227885
Author: Peter Krempa <pkrempa@xxxxxxxxxx>
Date:   Fri Jun 12 15:53:05 2015 +0200

    qemu: emulatorpin: Don't reset pinning when pinning to all cpus

    Similarly to a02a161bb8a6caf0db4dd446ed1cdf53d97b40 remove the default
    pinning assumption from emulatorpin.

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

commit c4bdfafcbb9ed00fa450d302acf9cf7929f24fc4
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Mon Jun 15 13:13:27 2015 +0200

    getOldStyleBlockDevice: Adjust formatting

    Instead of initializing return value to zero (success) and overwriting
    it on every failure just before the control jumps onto 'out' label,
    let's initialize to an error value and set to zero only when we are
    sure about the success. Just follow the pattern we have in the rest of
    the code.

    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 71b66bec2bd54e991a506834a3834d4513970c65
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Mon Jun 15 13:13:27 2015 +0200

    getNewStyleBlockDevice: Adjust formatting

    Instead of initializing return value to zero (success) and overwriting
    it on every failure just before the control jumps onto 'out' label,
    let's initialize to an error value and set to zero only when we are
    sure about the success. Just follow the pattern we have in the rest of
    the code.

    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 84020f9a398f739ee2cf7588a7cf3b4b0c077984
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Tue Jun 9 18:15:39 2015 -0400

    storage: Disallow wiping an extended disk partition

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

    Check if the disk partition to be wiped is the extended partition, if
    so then disallow it. Do this via changing the wipeVol backend to check
    the volume before passing to the common virStorageBackendVolWipeLocal

commit 243bbcc5dbce4e9fea863f1d59c2d22b1e1156b4
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Mon Jun 15 10:38:21 2015 +0200

    qemu caps: spell queue

commit 4fce9e84798be1441d8bc5b96f0ed68589e85222
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Tue Jun 9 16:49:00 2015 -0400

    qemu: Do not support 'serial' scsi-block 'lun' devices

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

    Seems the property has been deprecated for qemu, although seemingly ignored.

    This patch enforces from a libvirt perspective that a scsi-block 'lun'
    device should not provide the 'serial' property.

commit 1feaccf0001794e167b0374abf75d97024414e27
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Mon Jun 8 18:41:28 2015 -0400

    storage: Need to set secrettype for direct iscsi disk volume

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

    Commit id '1b4eaa61' added the ability to have a mode='direct' for
    an iscsi disk volume.  It relied on virStorageTranslateDiskSourcePool
    in order to copy any disk source pool authentication information to
    the direct disk volume, but it neglected to also copy the 'secrettype'
    field which ends up being used in the domain volume formatting code.
    Adding a secrettype for this case will allow for proper formatting later
    and allow disk snapshotting to work properly

    Additionally libvirtd restart processing would fail to find the domain
    since the translation processing code is run after domain xml processing,
    so handle the the case where the authdef could have an empty secrettype
    field when processing the auth and additionally ignore performing the
    actual and expected auth secret type checks for a DISK_VOLUME since that
    data will be reassembled later during translation processing of the
    running domain.

commit f8867012900ab124a7b09b0022155b4f1d950d52
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Thu Jun 11 16:15:46 2015 +0200

    virCapabilitiesDomainDataLookup: Produce saner error message

    During a review, I've noticed this error message that was eventually
    produced when I was trying to define a domain:

    error: invalid argument: could not find capabilities for arch=mips64el
    domaintype=(null)

    Look at the (null). Why is it there? Well, during XML parsing, we try
    to look up the default emulator for given OS type and possibly virt
    type too. And this is the problem, because if we don't want to look up
    by virt type, a -1 is passed to note this fact. Later, the code
    handles -1 just right. Except for error message. When it is
    constructed (in a very fabulous way I must say), the value is compared
    to zero, not -1. And since we don't have any translation from -1 to a
    virt type string, we just print (null).

    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

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

 


Rackspace

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