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

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

flight 131147 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. 131070

Tests which did not succeed, but are not blocking:
 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-amd64-i386-libvirt       1 build-check(1)               blocked  n/a
 test-armhf-armhf-libvirt-raw 13 saverestore-support-check    fail  like 131070
 test-armhf-armhf-libvirt     14 saverestore-support-check    fail  like 131070
 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-amd64-amd64-libvirt-vhd 12 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              081bdb4d68405aa3c6aa940f27e2464b5f339d65
baseline version:
 libvirt              eed7b205c4b9b6e490b23b16ba5e0cf3ad718a9e

Last test of basis   131070  2018-12-06 00:15:24 Z    3 days
Failing since        131116  2018-12-07 08:40:48 Z    2 days    2 attempts
Testing same since   131147  2018-12-08 11:19:46 Z    1 days    1 attempts

People who touched revisions under test:
  Daniel P. Berrangé <berrange@xxxxxxxxxx>
  Jim Fehlig <jfehlig@xxxxxxxx>
  John Ferlan <jferlan@xxxxxxxxxx>
  Michal Privoznik <mprivozn@xxxxxxxxxx>

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

Explanation of these reports, and of osstest in general, is at

Test harness code can be found at

Not pushing.

commit 081bdb4d68405aa3c6aa940f27e2464b5f339d65
Author: Daniel P. Berrangé <berrange@xxxxxxxxxx>
Date:   Thu Nov 1 11:42:56 2018 +0000

    tests: fix dry run handling in network firewall test
    The networkxml2firewalltest sets virCommand to dry run mode but doesn't
    provide a callback to fill in stdout/stderr. As a result when the
    firewall code queries rules it gets a NULL output and so never triggers
    the callback to process output.
    This trivial change just returns an empty string for the command output
    in order to ensure the callback gets triggered. It has no effect right
    now, but in future patches this will trigger greater test coverage.
    Reviewed-by: Laine Stump <laine@xxxxxxxxx>
    Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx>

commit 0367524b4f7003aec5e428aa9380fedf6f490c77
Author: Daniel P. Berrangé <berrange@xxxxxxxxxx>
Date:   Thu Nov 1 10:30:42 2018 +0000

    tests: remove duplicated test case in networkxml2firewalltest
    Reviewed-by: Laine Stump <laine@xxxxxxxxx>
    Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx>

commit 2deb74f1fecb5121483900b8ddea5ff6239489d9
Author: Daniel P. Berrangé <berrange@xxxxxxxxxx>
Date:   Wed Oct 31 18:51:34 2018 +0000

    util: refactor iptables APIs to share more code
    Most of the iptables APIs share code for the add/delete paths, but a
    couple were separated. Merge the remaining APIs to facilitate future
    Reviewed-by: Laine Stump <laine@xxxxxxxxx>
    Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx>

commit 84e7d8f4614a5771bc815145713ae0dd2520dcd3
Author: Jim Fehlig <jfehlig@xxxxxxxx>
Date:   Fri Nov 16 15:20:04 2018 -0700

    news: Mention Xen support for openvswitch
    Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 0a1b5653825bf67d3893a9177e188a131daba157
Author: Jim Fehlig <jfehlig@xxxxxxxx>
Date:   Fri Nov 16 13:08:23 2018 -0700

    xenconfig: add support for openvswitch configuration
    Add support for converting openvswitch interface configuration
    to/from libvirt domXML and xl.cfg(5). The xl config syntax for
    virtual interfaces is described in detail in the
    xl-network-configuration(5) man page. The Xen Networking wiki
    also contains information and examples for using openvswitch
    in xl.cfg config format
    Tests are added to check conversions of openvswitch tagged and
    trunked VLAN configuration.
    Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit de09ae2f4676dd521f558d383d33f4b4c026984c
Author: Jim Fehlig <jfehlig@xxxxxxxx>
Date:   Tue Jun 28 14:20:02 2016 -0600

    libxl: support openvswitch interfaces
    It is currently possible to use <interface>s of type openvswitch
    with the libxl driver in a non-standard way, e.g.
      <interface type='bridge'>
        <source bridge='ovsbr0'/>
        <mac address='00:16:3e:7a:35:ce'/>
        <script path='vif-openvswitch'/>
    This patch adds support for openvswitch <interface>s specified
    in typical libvirt config
      <interface type='bridge'>
        <source bridge='ovsbr0'/>
        <mac address='00:16:3e:7a:35:ce'/>
        <virtualport type='openvswitch'/>
    VLAN tags and trunking are also supported using the extended
    syntax for specifying an openvswitch bridge in libxl
    See Xen's networking wiki for more details on openvswitch support
    Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxx>
    ACKed-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 61d1253364d1fb21acf0e849f5aebf48ddc59bd4
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Tue Nov 27 10:12:56 2018 -0500

    qemu: Don't fail stats collection due to IOThread capability
    Commit 212dc9286 made a generic qemuDomainGetIOThreadsMon which
    would fail if the QEMU_CAPS_OBJECT_IOTHREAD didn't exist. Then
    commit d1eac927 used that helper for the collection of all domain
    stats. However, if the capability doesn't exist, then the entire
    stats collection fails. Since the IOThread stats were meant to be
    if available only, thus rather than failing if the capability
    doesn't exist, let's just not collect the stats. Restore the caps
    failure logic for qemuDomainGetIOThreadsLive.
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    Reviewed-by: Ján Tomko <jtomko@xxxxxxxxxx>

commit e1fc7ec08143eca29a9f449de000d04b9bbe09a0
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Tue Nov 27 10:08:53 2018 -0500

    qemu: Save qemuDomainGetStats error
    During qemuConnectGetAllDomainStats if qemuDomainGetStats causes
    a failure, then when collecting more than one domain's worth of
    statistics the loop in virDomainStatsRecordListFree would call
    virDomainFree which would call virResetLastError effectively wiping
    out the reason we failed leaving the caller with no idea why the
    collection failed.
    To fix this, let's Preserve the error and Restore it prior to return
    so that a caller such as 'virsh domstats' doesn't get the generic
    "error: An error occurred, but the cause is unknown".
    Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx>
    Reviewed-by: Ján Tomko <jtomko@xxxxxxxxxx>

Xen-devel mailing list



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