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

[libvirt test] 131894: regressions - trouble: blocked/broken/fail/pass

flight 131894 libvirt real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-libvirt-xsm    <job status>                 broken
 test-amd64-amd64-libvirt-xsm  4 host-install(4)        broken REGR. vs. 131857
 build-i386-libvirt            6 libvirt-build            fail REGR. vs. 131857

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       1 build-check(1)               blocked  n/a
 test-amd64-i386-libvirt-pair  1 build-check(1)               blocked  n/a
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a
 test-armhf-armhf-libvirt     14 saverestore-support-check    fail  like 131857
 test-armhf-armhf-libvirt-raw 13 saverestore-support-check    fail  like 131857
 test-amd64-amd64-libvirt     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     13 migrate-support-check        fail   never pass
 test-armhf-armhf-libvirt-raw 12 migrate-support-check        fail   never pass

version targeted for testing:
 libvirt              c39a0993dc509702f375b5ed55cbcbcdd6a9ca23
baseline version:
 libvirt              45b439c3af000eb41c819068d093406810dd036c

Last test of basis   131857  2019-01-09 04:18:51 Z    1 days
Testing same since   131894  2019-01-10 04:18:50 Z    0 days    1 attempts

People who touched revisions under test:
  Daniel P. Berrangé <berrange@xxxxxxxxxx>
  Michal Privoznik <mprivozn@xxxxxxxxxx>
  Yuval Shaia <yuval.shaia@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                                 broken  
 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

broken-job test-amd64-amd64-libvirt-xsm broken
broken-step test-amd64-amd64-libvirt-xsm host-install(4)

Not pushing.

commit c39a0993dc509702f375b5ed55cbcbcdd6a9ca23
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Wed Jan 9 17:18:58 2019 +0100

    src/qemu: Fix indentation in Makefile.inc.am
    Three lines are a bit off there.
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>
    Reviewed-by: Erik Skultety <eskultet@xxxxxxxxxx>

commit c10a6d50a40c062f37f5944de46b12bde66d3cbb
Author: Daniel P. Berrangé <berrange@xxxxxxxxxx>
Date:   Mon Dec 24 15:09:25 2018 +0000

    lxc: allow empty path in URI for historical compatibility
    The use of 'lxc://' was mistakenly broken in:
      commit 4c8574c85c554e68de0d8bf9b85727954a5bea91
      Author: Daniel P. Berrangé <berrange@xxxxxxxxxx>
      Date:   Wed Mar 28 12:49:29 2018 +0100
        driver: ensure NULL URI isn't passed to drivers with whitelisted URIs
    Allow it again for historical compatibility.
    Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx>

commit f886271410cf8b64ce92d0f727efe1b9a922c8c7
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Wed Jan 9 11:27:15 2019 +0100

    qemu: Use ULL instead of uint64_t for RDMA GID event
    In the previous commit we are using uint64_t for storing subnet
    prefix and interface id that qemu reports in
    RDMA_GID_STATUS_CHANGED event. We also report them in some debug
    messages. This poses a problem because uint64_t can be UL or ULL
    depending on the host architecture and hence we wouldn't know
    which format to use. Switch to ULL which is big enough and
    doesn't suffer from the issue.
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit ed357cef18b21c26f15e342b712a7de3f28f9471
Author: Yuval Shaia <yuval.shaia@xxxxxxxxxx>
Date:   Mon Dec 24 12:15:12 2018 +0200

    qemu: Process RDMA GID state change event
    This event is emitted on the monitor when a GID table in pvrdma device
    is modified and the change needs to be propagate to the backend RDMA
    device's GID table.
    The control over the RDMA device's GID table is done by updating the
    device's Ethernet function addresses.
    Usually the first GID entry is determine by the MAC address, the second
    by the first IPv6 address and the third by the IPv4 address. Other
    entries can be added by adding more IP addresses. The opposite is the
    same, i.e. whenever an address is removed, the corresponding GID entry
    is removed.
    The process is done by the network and RDMA stacks. Whenever an address
    is added the ib_core driver is notified and calls the device driver's
    add_gid function which in turn update the device.
    To support this in pvrdma device we need to hook into the create_bind
    and destroy_bind HW commands triggered by pvrdma driver in guest.
    Whenever a changed is made to the pvrdma device's GID table a special
    QMP messages is sent to be processed by libvirt to update the address of
    the backend Ethernet device.
    Signed-off-by: Yuval Shaia <yuval.shaia@xxxxxxxxxx>
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

osstest-output mailing list



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