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

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



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

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-libvirt-vhd  7 host-ping-check-xen       fail REGR. vs. 62098
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 16 
guest-start/debianhvm.repeat fail REGR. vs. 62098

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt-qcow2  9 debian-di-install            fail never pass
 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-xsm 12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt      12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-pair 21 guest-migrate/src_host/dst_host 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-amd64-amd64-libvirt-qcow2 11 migrate-support-check        fail never pass
 test-amd64-i386-libvirt-qcow2 11 migrate-support-check        fail  never pass
 test-amd64-amd64-libvirt-raw 11 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-amd64-libvirt-pair 21 guest-migrate/src_host/dst_host fail never 
pass
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check 
fail never pass
 test-amd64-i386-libvirt-vhd  11 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-raw  11 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-vhd 11 migrate-support-check        fail   never pass
 test-armhf-armhf-libvirt-raw  9 debian-di-install            fail   never pass

version targeted for testing:
 libvirt              79ccfec803ed939a32e569baa9a2b11022ec48b7
baseline version:
 libvirt              636a99058758a0447482f3baad94de8de3ab1151

Last test of basis    62098  2015-09-17 15:17:14 Z    5 days
Testing same since    62175  2015-09-19 22:23:48 Z    2 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Chunyan Liu <cyliu@xxxxxxxx>
  Jiri Denemark <jdenemar@xxxxxxxxxx>

jobs:
 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            fail    
 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                                fail    
 test-amd64-i386-libvirt-pair                                 fail    
 test-amd64-amd64-libvirt-qcow2                               pass    
 test-armhf-armhf-libvirt-qcow2                               fail    
 test-amd64-i386-libvirt-qcow2                                pass    
 test-amd64-amd64-libvirt-raw                                 pass    
 test-armhf-armhf-libvirt-raw                                 fail    
 test-amd64-i386-libvirt-raw                                  pass    
 test-amd64-amd64-libvirt-vhd                                 pass    
 test-armhf-armhf-libvirt-vhd                                 fail    
 test-amd64-i386-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


Not pushing.

------------------------------------------------------------
commit 79ccfec803ed939a32e569baa9a2b11022ec48b7
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Fri Sep 11 00:14:59 2015 +0200

    qemu: Fix some corner cases in persistent migration
    
    When persistently migrating a domain to a destination host where the
    same domain already exists (i.e., it is persistent and shutdown at the
    destination), we would happily throw away the original persistent
    definition without properly freeing it. And when updating the definition
    fails for some reason we don't properly revert to the original state
    leaving the domain broken.
    
    In addition to fixing these issues, the patch also makes sure the domain
    definition parsed from a migration cookie is either used or freed.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit c641d5508341352926e7b52a7746c9dd8acb9283
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Tue Jul 7 15:54:39 2015 +0200

    qemu: Queue events in migration Finish phase ASAP
    
    For quite a long time we don't need to postpone queueing events until
    the end of the function since we no longer have the big driver lock.
    Let's make the code of qemuMigrationFinish simpler by queuing events at
    the time we generate them.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit cda2afac79956a8437c47d2ea99e7f35e9e1b34a
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Tue Jul 7 15:33:53 2015 +0200

    qemuDomainEventQueue: Check if event is non-NULL
    
    Every single call to qemuDomainEventQueue() uses the following pattern:
    
        if (event)
            qemuDomainEventQueue(driver, event);
    
    Let's move the check for valid event to qemuDomainEventQueue and
    simplify all callers.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit 5f7ad327783a727aacdc29b60fe934efb2039310
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Tue Jul 7 15:29:10 2015 +0200

    qemu: Don't report false errors in migration protocol v2
    
    Finish is the final state in v2 of our migration protocol. If something
    fails, we have no option to abort the migration and resume the original
    domain. Non fatal errors (such as failure to start guest CPUs or make
    the domain persistent) has to be treated as success. Keeping the domain
    running while reporting the failure was just asking for trouble.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit cc40c28410300f5e2a389628e1f71fa86207fb49
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Tue Jul 7 14:42:42 2015 +0200

    qemu: Kill domain when migration finish fails
    
    Whenever something fails during incoming migration in Finish phase
    before we started guest CPUs, we need to kill the domain in addition to
    reporting the failure.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit f5c509623fc49f30c17ff539aeaeda6ad2179c03
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Tue Jul 7 14:15:31 2015 +0200

    qemu: Don't fail migration on save status failure
    
    When we save status XML at the point during migration where we have
    already started the domain on destination, we can't really go back and
    abort migration. Thus the only thing we can do is to log a warning and
    report success.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit 8874d37f94ca71ac0954183883f98ca1d3df0acc
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Tue Jul 7 14:11:58 2015 +0200

    qemu: Simplify qemuMigrationFinish
    
    Offline migration is quite special because we don't really need to do
    anything but make the domain persistent. Let's do it separately from
    normal migration to avoid cluttering the code with
    !(flags & VIR_MIGRATE_OFFLINE).
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit a86b188567e44c736d59c72fc55b08c86274f94e
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Tue Jul 7 12:11:37 2015 +0200

    qemu: Split qemuMigrationFinish
    
    Separate code which makes incoming domain persistent into
    qemuMigrationPersist.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit 56945e1374bd254148643d76a98fba9be67fba15
Author: Chunyan Liu <cyliu@xxxxxxxx>
Date:   Thu Sep 17 01:15:22 2015 -0400

    libxl: fix AttachDeviceConfig on hostdev type
    
    After attach-device a <hostdev> with --config, new device doesn't
    show up in dumpxml and in guest.
    
    To fix that, set dev->data.hostdev = NULL after work so that the
    pointer is not freed, since vmdef has the pointer and still need it.
    
    Signed-off-by: Chunyan Liu <cyliu@xxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

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