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

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

flight 131287 libvirt real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-i386-libvirt            6 libvirt-build            fail REGR. vs. 131219
 test-amd64-amd64-libvirt-vhd 11 guest-start              fail REGR. vs. 131219

Tests which did not succeed, but are not blocking:
 test-amd64-i386-libvirt       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-i386-libvirt-pair  1 build-check(1)               blocked  n/a
 test-armhf-armhf-libvirt-raw 13 saverestore-support-check    fail  like 131219
 test-armhf-armhf-libvirt     14 saverestore-support-check    fail  like 131219
 test-amd64-amd64-libvirt     13 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-xsm 13 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-armhf-armhf-libvirt-raw 12 migrate-support-check        fail   never pass
 test-armhf-armhf-libvirt     13 migrate-support-check        fail   never pass

version targeted for testing:
 libvirt              3972a25f1d4f9c75d73faaac9106fc16037de645
baseline version:
 libvirt              fa30ee04a2a7205c3d664c67b88dd8df9cb1fb40

Last test of basis   131219  2018-12-11 04:19:05 Z    3 days
Failing since        131256  2018-12-12 04:19:19 Z    2 days    2 attempts
Testing same since   131287  2018-12-13 04:53:27 Z    1 days    1 attempts

People who touched revisions under test:
  Daniel P. Berrangé <berrange@xxxxxxxxxx>
  Erik Skultety <eskultet@xxxxxxxxxx>
  John Ferlan <jferlan@xxxxxxxxxx>
  Julio Faracco <jcfaracco@xxxxxxxxx>
  Michal Privoznik <mprivozn@xxxxxxxxxx>
  Nikolay Shirokovskiy <nshirokovskiy@xxxxxxxxxxxxx>

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

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

Not pushing.

commit 3972a25f1d4f9c75d73faaac9106fc16037de645
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Fri Dec 7 09:46:48 2018 -0500

    conf: Add check/error for domain supports cold/hotplug
    Add a check during virDomainDefCompatibleDevice whether the
    domain supports cold/hotplug of a memory module even though
    this duplicates the qemuDomainDefValidateMemoryHotplug check.
    Without this check, the cold/hot plug would fail on the
    subsequent mem_memory check (since it's 0). Adding a check
    for max_memory > 0 would allow the subsequent hotplug check
    to fail, but would cause coldplug to fail with the somewhat
    opaque message "no free memory device slot available".
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 4f0854e7dfdd4f7206008439f3a8d15bd373a776
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Fri Dec 7 11:07:32 2018 -0500

    conf: Add the size of failed max_memory in error
    If virDomainDefCompatibleDevice fails because there is insufficient
    domain def->mem.max_memory, then let's also print out that value in
    the error message.
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit dd45c2710f6fd2d4f8a47f97960532d0e0091e7d
Author: Erik Skultety <eskultet@xxxxxxxxxx>
Date:   Fri Dec 7 14:53:46 2018 +0100

    conf: domain: gfx: Iterate over graphics devices when doing validation
    The QEMU validation code for graphics has been in place for a while, but
    because it is only executed from virDomainDeviceInfoIterateInternal, it
    was never run, since the iterator expects the device to have boot info
    which graphics don't have. The unfortunate side effect of this whole mess
    was that a few capabilities were missing from the test suite (as commit
    d8266ebe1 demonstrated with graphics-spice-invalid-egl-headless test),
    which in turn meant that a few graphics tests which expected a failure
    happily accepted any failure the test runtime returned which made them
    succeed. The impact of this was that we then allowed to start a domain
    with multiple OpenGL-enabled graphics devices.
    This patch enables iteration over graphics devices. Unsurprisingly,
    a few tests started to fail as a result, so fix those too.
    Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit 0d5244cc867155f7548e568f298799d639017698
Author: Erik Skultety <eskultet@xxxxxxxxxx>
Date:   Fri Dec 7 13:13:58 2018 +0100

    tests: Introduce negative versions of DO_TEST_CAPS_LATEST
    It's fairly easy to forget to add a capability to the list of
    capabilities for a negative test case which might yield (for us) very
    unfortunate results. Therefore, introduce negative versions of
    DO_TEST_CAPS_LATEST macros, so that real QEMU caps can be used with
    tests that expect a failure too.
    Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit 88d24aaccc1e31ff1ce682f9496cf08cc7f7c216
Author: Erik Skultety <eskultet@xxxxxxxxxx>
Date:   Fri Dec 7 13:13:03 2018 +0100

    conf: domain: Introduce virDomainDeviceIterateFlags
    Validation of domain devices is accomplished via a generic device
    iterator which takes a callback, iterates over all kinds of supported
    device types and invokes the callback on every single device. However,
    there might be cases when we need to alter the behaviour of the
    iteration (most notably skip or include a group of devices). Therefore,
    this patch introduces iterator flags.
    Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit 414c51b7a11cc52c4276c7220d0b973c57c725d6
Author: Erik Skultety <eskultet@xxxxxxxxxx>
Date:   Fri Dec 7 15:07:37 2018 +0100

    qemu: domain: gfx: Fix shadowing of a function argument in validation
    Since the code was never run, it would have been very hard to spot this
    mistake, especially since the compiler can't really warn about it.
    Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit daf4e2abca914fd8340d2243e2cb070a43dd7149
Author: Julio Faracco <jcfaracco@xxxxxxxxx>
Date:   Fri Nov 30 20:43:37 2018 +0800

    tests: Adding test case to include multiple network definitions.
    This commit includes a test case for multiple network definitions. It is
    useful right now, but it will be more useful when the index used by LXC
    version 3.X is implemented to support this new settings. The version 3.X
    is using indexes to specify each network settings.
    Signed-off-by: Julio Faracco <jcfaracco@xxxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 53762677a84c7bf124714d9e607da8c115084775
Author: Julio Faracco <jcfaracco@xxxxxxxxx>
Date:   Fri Nov 30 20:43:36 2018 +0800

    lxc: Initializing IPv6 and IPv4 gateway to overwrite old settings.
    This commit fixes a bug when you have multiple network settings defined.
    Basically, if you set an IPv6 or IPv4 gateway, it carries on next
    network settings. It is happening because the data is not being
    initialized when a new network type is defined. So, the old data still
    persists into the pointer. Another way to initialized the data was
    introduced using memset() to avoid missing attributes from the struct.
    Signed-off-by: Julio Faracco <jcfaracco@xxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit 34eca98522c1bd39e18f1eceee4f888dad173e5e
Author: Daniel P. Berrangé <berrange@xxxxxxxxxx>
Date:   Tue Dec 11 14:58:43 2018 +0000

    tools: rename S_ORG to C_ORG in virt-pki-validate
    Rename a variable to make it clear that it holds the client organization
    rather than the server organization.
    Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx>

commit ecf8619430f78b8b2beeb57c239cc78f6e3907bd
Author: Daniel P. Berrangé <berrange@xxxxxxxxxx>
Date:   Mon Dec 10 16:50:10 2018 +0000

    tools: relax x509 Subject regexes to allow numbers and more
    The virt-pki-validate tool is extracting components in the x509
    certificate Subject field. Unfortunately the regex it is is using is far
    too strict, and so truncating valid data. It needs to consider ',' as a
    field separator, and if that's not there take all data until the EOL.
    With the broken regex:
    $ echo "  Subject: O=Test,CN=guestHyp1ver"  | sed 's+.*CN=\(.[a-zA-Z 
    And with the fixed regex
    $ echo "Subject: O=Test,CN=guestHyp1ver"  | sed 's+.*CN=\([^,]*\).*+\1+'
    Reported-by: Kashyap Chamarthy <kchamart@xxxxxxxxxx>
    Reviewed-by: Kashyap Chamarthy <kchamart@xxxxxxxxxx>
    Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx>

commit 1215195fd882efac47c07c16bfff0ad9a33c45a3
Author: Erik Skultety <eskultet@xxxxxxxxxx>
Date:   Thu Dec 6 16:12:14 2018 +0100

    domain: conf: graphics: Fix picking DRI renderer automatically for SPICE
    Commit 255e0732 introduced a few graphics-related helpers. The problem
    is that virDomainGraphicsNeedsAutoRenderNode returns true if it gets
    NULL as a response from virDomainGraphicsNeedsAutoRenderNode. That's
    okay for egl-headless because that one always needs a DRM render node,
    the same is not true for SPICE though, and unless the XML specifies
    <gl enable='yes'> for SPICE, there's no need for any renderer.
    Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx>
    Reviewed-by: Ján Tomko <jtomko@xxxxxxxxxx>

commit 067aad26befafb446e8a0d5c83d1a4d3b7f704d9
Author: Nikolay Shirokovskiy <nshirokovskiy@xxxxxxxxxxxxx>
Date:   Fri Nov 9 10:50:47 2018 +0300

    qemu: disable external snapshot of readonly disk
    Disable external snapshot of a readonly disk for domains as
    this operation is not very useful. Such a snapshot is not
    possible for active domains but the error message from QEMU
    is more cryptic:
         error: internal error: unable to execute QEMU command 'transaction':
                             Could not create file: Permission denied
    This error at least makes the error more understandable for
    active domains and disallows for inactive domains as well.
    Signed-off-by: Nikolay Shirokovskiy <nshirokovskiy@xxxxxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

Xen-devel mailing list



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