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

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



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

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-arm64-arm64-libvirt        <job status>                 broken
 test-arm64-arm64-libvirt-xsm  6 xen-install              fail REGR. vs. 123189

Tests which are failing intermittently (not blocking):
 test-arm64-arm64-libvirt      4 host-install(4)          broken pass in 123212

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

version targeted for testing:
 libvirt              4804a4db33a37f828d033733bc47f6eff5d262c3
baseline version:
 libvirt              b9eb0145eb3879c63152227afc0be0a1f5b8514a

Last test of basis   123189  2018-05-25 07:51:05 Z    2 days
Testing same since   123212  2018-05-26 09:44:19 Z    1 days    2 attempts

------------------------------------------------------------
People who touched revisions under test:
  Jiri Denemark <jdenemar@xxxxxxxxxx>
  John Ferlan <jferlan@xxxxxxxxxx>
  Michal Privoznik <mprivozn@xxxxxxxxxx>
  Roland Schulz <schullzroll@xxxxxxxxx>

jobs:
 build-amd64-xsm                                              pass    
 build-arm64-xsm                                              pass    
 build-armhf-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-arm64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-arm64-libvirt                                          pass    
 build-armhf-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-arm64-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-arm64-arm64-libvirt-xsm                                 fail    
 test-armhf-armhf-libvirt-xsm                                 pass    
 test-amd64-i386-libvirt-xsm                                  pass    
 test-amd64-amd64-libvirt                                     pass    
 test-arm64-arm64-libvirt                                     broken  
 test-armhf-armhf-libvirt                                     pass    
 test-amd64-i386-libvirt                                      pass    
 test-amd64-amd64-libvirt-pair                                pass    
 test-amd64-i386-libvirt-pair                                 pass    
 test-arm64-arm64-libvirt-qcow2                               pass    
 test-armhf-armhf-libvirt-raw                                 pass    
 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

broken-job test-arm64-arm64-libvirt broken
broken-step test-arm64-arm64-libvirt host-install(4)

Not pushing.

------------------------------------------------------------
commit 4804a4db33a37f828d033733bc47f6eff5d262c3
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Sat May 19 08:00:58 2018 -0400

    schema: Add missing block data for nodedev
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1566416
    
    Commit id 'fe2af45b' added output for logical_block_size and
    num_blocks for both removeable and fixed storage, but did not
    update the nodedev capability causing virt-xml-validate to fail.
    It's listed as optional only because it only prints if the
    sizes are > 0. For a CDROM drive the values won't be formatted.
    
    Update the nodedevxml2xmltest in order to output the values
    for storage based on the logic from udevProcessRemoveableMedia
    and udevProcessSD with respect to the logical_blocksize and
    num_blocks calculations.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by Michal Privoznik <mprivozn@xxxxxxxxxx>

commit c1a0601debfe2c84160234cf6269606f4198faa0
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Sat May 19 07:02:47 2018 -0400

    schema: Fix capability grammar for pagesElem
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1572491
    
    Commit id '02129b7c0' added a single pagesElem for slightly
    different purposes. One usage was an output for host page size
    listing and the other for NUMA supported page sizes. For the
    former, only the pages unit and size are formatted, while for
    the latter the pages unit, size, and availability data is formatted.
    
    The virt-xml-validate would fail because it expected something
    extra in the host page size output. So split up pagesElem a bit
    and create pagesHost and pagesNuma for the differences.
    
    Modify some capabilityschemadata output to have the output - even
    though the results may not be realistic with respect to the
    original incarnation of the data.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by Michal Privoznik <mprivozn@xxxxxxxxxx>

commit f97c4cc5e130ada351890a1f4f1ca65b1cf6d69d
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Sat May 19 06:47:27 2018 -0400

    schema: Add microcode element to capability grammar
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1572491
    
    Commit id 'd2440f3b5' added printing the <microcode> for the
    capabilities, but didn't update the capabilities schema.
    
    While at it, update capabilityschemadata for caps-test2
    and caps-test3 to output some value for validation.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 8d84578035e7c88b62555582ba938fef03cd30bd
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Fri May 18 18:25:54 2018 -0400

    schema: Add vzmigr for host migrate transport capability
    
    Commit id '0eced74f3' added vzmigr as a valid option for
    virCapabilitiesAddHostMigrateTransport, but didn't update
    the capabilities schema resulting in possible virt-xml-validate
    failure.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 4cfa9309dc16ef58fd4174e886c5fdcf97f5f4e6
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Fri May 18 18:00:23 2018 -0400

    schema: Add rdma for host migrate transport capability
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1572491
    
    Commit id 'b3fd95e36' added rdma as a valid option for
    virCapabilitiesAddHostMigrateTransport, but didn't update
    the capabilities schema resulting in possible virt-xml-validate
    failure.
    
    While at it, update the capabilityschemadata for caps-qemu-kvm
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by Michal Privoznik <mprivozn@xxxxxxxxxx>

commit dcd9db75feb8ad6091717af546e7696282faa124
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Fri May 18 17:47:08 2018 -0400

    schema,tests: Use vpxmigr for host migrate transport capability
    
    Commit id 'e4938ce2f' changed the esx_driver to use 'vpxmigr'
    instead of esx for virCapabilitiesAddHostMigrateTransport, so
    update the capabilities to allow virt-xml-validate to pass and
    update the test to use the newer name.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 7ed598438687feaddaf0a653d7cbb8a1c1ad4933
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Fri May 18 18:05:07 2018 -0400

    schema: Remove xenmigr from host migrate transport capability
    
    Commit id '1dac5fbb' removed xenmigr as a capability option
    for virCapabilitiesAddHostMigrateTransport but didn't update
    the schema resulting in possible failure for virt-xml-validate.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 39d76c68569fa4a1816172e0d971a6b148ba5c23
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Fri May 18 17:25:01 2018 -0400

    schema: Add physical sizing element for storagevol grammar
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1572491
    
    Commit id '78661cb' added a physical output, but failed to update
    the schema resulting in a failure from virt-xml-validate.
    
    While at it - update the storagevolschemadata for the output.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by Michal Privoznik <mprivozn@xxxxxxxxxx>

commit e288080ae02d357412755d998bd542d4cb60c8b2
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Thu May 24 11:10:57 2018 -0400

    disk: Allow settling to occur after reading partitions
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1400475
    
    In order to avoid a possible error as a result of kernel interactions
    with the partition helper, let's use virWaitForDevices to force things
    to settle down before attempting to open and read the partition. This
    is related to https://bugzilla.redhat.com/show_bug.cgi?id=1264719.
    
    Although perhaps overkill to have too many places to settle, since
    we know that the act of reading the partitions via libvirt_parthelper
    will cause udev activity/events - we just need to ensure udev has
    been settled before proceding with usage of the device.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 509abc40d402a67a61aae95089c101be104a5537
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Wed Apr 11 16:01:54 2018 -0400

    docs: Add news article for VM Generation ID
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 0f358fcdcad6c814fca0325349c77c724da9bd21
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Fri Apr 27 08:16:40 2018 -0400

    domcaps: Add 'genid' to domain capabilities
    
    Report domaincaps <features><genid supported='yes'/> if the guest
    config accepts <genid/> or <genid>$GUID</genid>.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 87973a45f97dcbf0c515d9104e068094a09c74b5
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Tue Mar 20 18:29:46 2018 -0400

    qemu: Add VM Generation ID to qemu command line
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1149445
    
    If the domain requests usage of the genid functionality,
    then add the QEMU '-device vmgenid' to the command line
    providing either the supplied or generated GUID value.
    
    Add tests for both a generated and supplied GUID value.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit c445abb52d3d7ab7869a4ba2b2c35e8e59c3a4f7
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Mon Apr 9 10:31:17 2018 -0400

    qemu: Alter VM Generation ID for specific startup/launch transitions
    
    Before we generate the command line for qemu, if the domain about to
    be launched desires to utilize the VM Generation ID functionality, then
    handle both the regenerating the GUID value for backup recovery (restore
    operation) and the startup after snapshot as both require a new GUID to
    be generated to allow the guest operating system to recognize the VM
    is re-executing something that has already executed before.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 3005002e0eac412704b33ac53e10b2428ec7d020
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Fri Mar 16 17:23:05 2018 -0400

    qemu: Add VM Generation ID device capability
    
    Add the query of the device objects for the vmgenid device
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit b50efe97ad1357f9dff26450daf68a7a53201bea
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Mon Apr 9 12:10:02 2018 -0400

    conf: Add VM Generation ID parse/format support
    
    The VM Generation ID is a mechanism to provide a unique 128-bit,
    cryptographically random, and integer value identifier known as
    the GUID (Globally Unique Identifier) to the guest OS. The value
    is used to help notify the guest operating system when the virtual
    machine is executed with a different configuration.
    
    This patch adds support for a new "genid" XML element similar to
    the "uuid" element. The "genid" element can have two forms "<genid/>"
    or "<genid>$GUID</genid>". If the $GUID is not provided, libvirt
    will generate one and save it in the XML.
    
    Since adding support for a generated GUID (or UUID like) value to
    be displayed modifying the xml2xml test to include virrandommock.so
    is necessary since it will generate a "known" value.
    
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit c7151b0e4d3f1115384c24d16d9338f84bab975b
Author: Roland Schulz <schullzroll@xxxxxxxxx>
Date:   Fri May 25 09:12:37 2018 +0200

    tools: virsh: Add virshCellnoCompleter.
    
    Signed-off-by: Roland Schulz <schullzroll@xxxxxxxxx>
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 11a2550c27176745a0f786abd5b99822931ca3c6
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Fri May 25 09:45:15 2018 +0200

    spec: Enable libssh on future RHEL
    
    Future RHEL will certainly be modern enough to support libssh.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

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