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

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

flight 85777 libvirt real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-libvirt-pair 4 host-install/dst_host(4) broken REGR. vs. 85689
 test-armhf-armhf-libvirt-qcow2  9 debian-di-install       fail REGR. vs. 85689

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

version targeted for testing:
 libvirt              cf091094a42a2b43f8a3ea80694a784e6f2b4a47
baseline version:
 libvirt              eff43d9abac0e0df9779ee412b7aeaccea8f6e2a

Last test of basis    85689  2016-03-08 04:21:47 Z    1 days
Testing same since    85777  2016-03-09 04:24:39 Z    0 days    1 attempts

People who touched revisions under test:
  Andrea Bolognani <abologna@xxxxxxxxxx>
  Jiri Denemark <jdenemar@xxxxxxxxxx>
  Michal Privoznik <mprivozn@xxxxxxxxxx>

 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-qemuu-debianhvm-amd64-xsm           pass    
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm            pass    
 test-amd64-amd64-libvirt-xsm                                 pass    
 test-armhf-armhf-libvirt-xsm                                 fail    
 test-amd64-i386-libvirt-xsm                                  pass    
 test-amd64-amd64-libvirt                                     pass    
 test-armhf-armhf-libvirt                                     fail    
 test-amd64-i386-libvirt                                      pass    
 test-amd64-amd64-libvirt-pair                                broken  
 test-amd64-i386-libvirt-pair                                 pass    
 test-armhf-armhf-libvirt-qcow2                               fail    
 test-armhf-armhf-libvirt-raw                                 fail    
 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-step test-amd64-amd64-libvirt-pair host-install/dst_host(4)

Not pushing.

commit cf091094a42a2b43f8a3ea80694a784e6f2b4a47
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Thu Feb 18 00:12:33 2016 +0100

    qemu: Add support for job completed event
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit f28930018173e4dd2ae32a8f242ea109fe7ed83e
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Wed Feb 17 21:20:11 2016 +0100

    Introduce job completed event
    The VIR_DOMAIN_EVENT_ID_JOB_COMPLETED event will be triggered once a job
    (such as migration) finishes and it will contain statistics for the job
    as one would get by calling virDomainGetJobStats. Thanks to this event
    it is now possible to get statistics of a completed migration of a
    transient domain on the source host.
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit a2374edf08446c173a20d96d1b1a436883878c81
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Tue Feb 23 12:40:47 2016 +0100

    qemu: Do not report completed stats until the job finishes
    We would happily report and free statistics of a completed migration
    even before it actually completed (on the source host while migration is
    in the Finish phase).
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit cb483a68fdc3503efc9b0996570e58aaf0c11c17
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Tue Feb 23 10:47:01 2016 +0100

    qemu: Fix a race when computing migration downtime
    Computing a total downtime during a migration requires us to store a
    time stamp when guest CPUs get stopped. The value (and all other
    statistics) is then transferred to the destination to compute the
    downtime. Because the stopped time stamp is stored by a STOP event
    handler while the statistics which will be sent over to the destination
    are copied synchronously within qemuMigrationWaitForCompletion.
    Depending on the timing of STOP and MIGRATION events, we may end up
    copying (and transferring) statistics without the stopped time stamp
    set. Let's make sure we always use the correct time stamp.
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit 315808e99ec09d3894e79007728a70d891b5e02e
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Tue Jan 5 22:19:28 2016 +0100

    qemu: Don't explicitly stop CPUs after migration
    With a very old QEMU which doesn't support events we need to explicitly
    call qemuMigrationSetOffline at the end of migration to update our
    internal state. On the other hand, if we talk to QEMU using QMP, we
    should just wait for the STOP event and let the event handler update the
    state and trigger a libvirt event.
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit 5d01e8666b8119779d11f0aa58b8521d14a164ea
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Thu Feb 18 14:44:48 2016 +0100

    qemu: Properly update completed migration stats
    We should not overwrite all migration statistics on the source with the
    numbers sent by the destination since the source may have an updated
    view in some cases (such as post-copy migration). It's safer to update
    just the timing info we need to get from the destination and be prepared
    for the future. And we should only do all this after a successful
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit e031560e8719ee44bcedcc02019f13169858b8a3
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Thu Feb 18 14:02:15 2016 +0100

    qemu: Store completed stats at the very end of migration
    Statistics for a completed migration only make sense if the migration
    was successful. Let's not store them in priv->job.completed until we
    are sure it was a success.
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit 12a1631440c8db098bf4cba16e3fd4aca09951c4
Author: Andrea Bolognani <abologna@xxxxxxxxxx>
Date:   Thu Feb 25 14:50:54 2016 +0100

    hostdev: Remove explicit NULL checks
    NULL checks are performed implicitly in the rest of the module,
    including other allocations in the very same function.

commit a54de18a54facae8320e9fa9f927ffc31e240f08
Author: Andrea Bolognani <abologna@xxxxxxxxxx>
Date:   Wed Feb 24 13:44:09 2016 +0100

    hostdev: Fix indentation

commit a67b14a97516e796ecbb1da0b5a9b81985c645a0
Author: Andrea Bolognani <abologna@xxxxxxxxxx>
Date:   Mon Mar 7 14:14:54 2016 +0100

    hostdev: Remove inaccurate comment
    The comment claimed that virPCIDeviceReattach() does not reattach
    a device to the host driver; except it actually does, so the
    comment is just confusing and we're better off removing it.

commit be70acb7886d48811cec7030607122418ae76402
Author: Andrea Bolognani <abologna@xxxxxxxxxx>
Date:   Mon Feb 22 15:02:23 2016 +0100

    hostdev: Make comments easier to change later
    Replace the term "loop" with the more generic "step". This allows us
    to be more flexible and eg. have a step that consists in a single
    function call.
    Don't include the number of steps in the first comment of the
    function, so that we can add or remove steps without having to worry
    about keeping that comment in sync.
    For the same reason, remove the summary contained in that comment.
    Clean up some weird vertical spacing while we're at it.

commit 3632185617ddafd3ba7fdf652763cc8a97cbafaf
Author: Andrea Bolognani <abologna@xxxxxxxxxx>
Date:   Thu Mar 3 16:13:04 2016 +0100

    tests: hostdev: Group test cases
    Instead of considering each single step its own test case, create
    high level test cases that reproduce a certain scenario.

commit f8388cdce453be0fb9113edc312ac45e2ef59142
Author: Andrea Bolognani <abologna@xxxxxxxxxx>
Date:   Wed Mar 2 15:33:18 2016 +0100

    tests: hostdev: Add more checks on list size
    Always call CHECK_LIST_COUNT() to check the size of both the active
    and inactive devices list.

commit 4a9ea5048c409dce72c6b0e9e8fd9fb268457bb3
Author: Andrea Bolognani <abologna@xxxxxxxxxx>
Date:   Wed Mar 2 15:27:06 2016 +0100

    tests: hostdev: Use size_t for count variables
    virPCIDeviceListCount()'s return type is size_t, so variables that
    store its return value should be of that type.

commit ff087d8daefd6395f600dec27785b79edb662f69
Author: Andrea Bolognani <abologna@xxxxxxxxxx>
Date:   Wed Mar 2 15:23:51 2016 +0100

    tests: hostdev: Move variable declaration inside CHECK_LIST_COUNT()
    The 'actualCount' variable, formerly just 'count', is only used
    internally by the macro, so it's better to move its declaration
    inside the macro as well: this way, it doesn't have to be declared
    by every single user.
    The new name is less generic to make clashes less likely.

commit dd9f8e0292dbcc44563a1a1adb02c929f60ad28e
Author: Andrea Bolognani <abologna@xxxxxxxxxx>
Date:   Wed Mar 2 15:15:07 2016 +0100

    tests: hostdev: Use better variable names
    Change the extremely generic count1 and count2 to the more
    descriptive active_count and inactive_count.

commit 9f506fdb6be8a2d7b6b52b28eb65bfac7e040eb1
Author: Andrea Bolognani <abologna@xxxxxxxxxx>
Date:   Wed Mar 2 13:17:08 2016 +0100

    tests: hostdev: Remove magic numbers
    When checking the number of devices added to a device list, use the
    nhostdevs variable instead of its value, so that the test can keep
    working even if more hostdevs are added.

commit 18f231e6ff953c014f4ef0a75da7bf20c4f35de9
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Sat Mar 5 12:59:45 2016 +0100

    _virtualboxCreateMachine: Avoid unbounded stack
    If the stars are in the right position and you're building with
    VBox >= 4.2.0 it will happen that compiler thinks an array
    allocated on the stack may be unbounded:
    In file included from vbox/vbox_V4_2.c:13:0:
    vbox/vbox_tmpl.c: In function '_virtualboxCreateMachine':
    vbox/vbox_tmpl.c:2811:1: error: stack usage might be unbounded 
     _virtualboxCreateMachine(vboxGlobalData *data, virDomainDefPtr def, 
IMachine **machine, char *uuidstr ATTRIBUTE_UNUSED)
    Well, given how the variable is declared, I had some hard time
    seeing it is actually bounded. Surprisingly compiler does not
    complain because of -Wframe-larger-than. This is because
    variable length arrays do not count into that warning.
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

Xen-devel mailing list



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