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

[Xen-devel] [libvirt test] 115172: trouble: broken/pass



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

Failures and problems with tests :-(

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

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt-xsm 14 saverestore-support-check    fail  like 114825
 test-armhf-armhf-libvirt     14 saverestore-support-check    fail  like 114825
 test-armhf-armhf-libvirt-raw 13 saverestore-support-check    fail  like 114825
 test-amd64-i386-libvirt-xsm  13 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt      13 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-xsm 13 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-qcow2 12 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              55ac6a5d44a2fbd7e93d995930d6071030c907ba
baseline version:
 libvirt              08d4e16f88f9cb0e078b544f49a0647c8847fe95

Last test of basis   114825  2017-10-21 04:47:31 Z    3 days
Testing same since   115172  2017-10-24 04:20:11 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Jiri Denemark <jdenemar@xxxxxxxxxx>
  Michal Privoznik <mprivozn@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            broken  
 test-amd64-amd64-libvirt-xsm                                 pass    
 test-armhf-armhf-libvirt-xsm                                 pass    
 test-amd64-i386-libvirt-xsm                                  pass    
 test-amd64-amd64-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-amd64-i386-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-amd64-amd64-libvirt broken
broken-job test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm broken
broken-step test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm host-install(4)
broken-step test-amd64-amd64-libvirt host-install(4)

Not pushing.

------------------------------------------------------------
commit 55ac6a5d44a2fbd7e93d995930d6071030c907ba
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Thu Oct 19 14:26:24 2017 +0200

    qemu: Set correct job status when qemuMigrationRun fails
    
    Instead of enumerating all states which need to be turned into
    QEMU_DOMAIN_JOB_STATUS_FAILED (and failing to add all of them), it's
    better to mention just the one which needs to be left alone.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit 73a352263c1745da8a71f1a636ff805ad3e1d249
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Thu Oct 19 14:22:53 2017 +0200

    qemu: Consistently use exit_monitor in qemuMigrationRun
    
    Almost every failure in qemuMigrationRun while we are talking to QEMU
    monitor results in a jump to exit_monitor label. The only exception is
    removed by this patch.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit af32e57f8e5800ceca46b775276f4a4877ecf89a
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Thu Oct 19 14:21:00 2017 +0200

    qemu: Don't misuse "ret" in qemuMigrationRun
    
    The "ret" variable is used for storing the return value of a function
    and should not be used as a temporary variable.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit 7d2fbabcafaa357729a39331b015d759fc4213dd
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Thu Oct 19 14:15:46 2017 +0200

    qemu: Unite error handling in qemuMigrationRun
    
    Merge cancel and cancelPostCopy sections with the generic error section,
    where we can easily decide whether canceling the ongoing migration is
    required.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit c1a643b68f34040dee75959824759d527472e3c9
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Thu Oct 19 15:09:25 2017 +0200

    qemu: Split cleanup and error code in qemuMigrationRun
    
    Let cleanup only do things common to both failure and success paths and
    move error handling code inside the new "error" section.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit f8ede9cc234e4d167eda7eccf68f9d02d3a65821
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Wed Oct 18 15:34:31 2017 +0200

    qemu: Refactor qemuMigrationRun a bit
    
    Some code which was supposed to be executed only when migration
    succeeded was buried inside the cleanup code.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit 960326237764f8970250a3608e7b2b880e030715
Author: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date:   Tue Oct 17 21:27:55 2017 +0200

    qemu: Use switch in qemuMigrationCompleted
    
    When adding a new job state it's useful to let the compiler complain
    about places where we need to think about what to do with the new
    state.
    
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit 8bf6426d6eaf6fc2b4593927d2279ec36f75e0d3
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Fri Oct 20 16:19:07 2017 +0200

    news: Document user aliases
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 7e939394b23845a72ddee969a69b2d0b071a08bf
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Fri Oct 20 16:48:14 2017 +0200

    tests: Test user set aliases for qemu
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit f3bc68e22177e745d470ccaaa23f776779b7e95e
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Thu Oct 19 08:39:40 2017 +0200

    qemu: Parse alias from inactive XMLs
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1434451
    
    This way users can uniquely identify devices at define time.
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 93bc2c21267963eaea0183092aa03f31a3f7c79a
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Wed Oct 18 13:48:46 2017 +0200

    docs: Document user aliases
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 0429e52f19d77752658cbc4b745103188650b2ea
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Wed Oct 18 13:12:08 2017 +0200

    conf: Format alias even for inactive XMLs
    
    We need to format alias even for inactive XMLs since that's the
    way how users are going to identify their devices.
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 821b0b295d0dea21656a75bac34d4694ea28f4bd
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Tue Oct 17 13:13:08 2017 +0200

    qemuhotplugtest: Load active XML
    
    The point of this test is to load live XML and test hotplug. But
    even though the XMLs we are parsing are live, the parsing is done
    with VIR_DOMAIN_DEF_PARSE_INACTIVE flag.
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit a15c97f5e42324bb7be9c7afbac849b575a6926e
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Tue Oct 17 13:27:01 2017 +0200

    qemuxml2argvdata: Drop device aliases
    
    The qemuxml2argvtest expects the domain XMLs to be inactive ones.
    Therefore we should pass inactive XMLs.
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 92f41b3297192c7e0e3ced63398e9c08f5f8cbd3
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Tue Oct 17 10:42:54 2017 +0200

    qemuDomainABIStabilityCheck: Check for memory aliases too
    
    Since we will be allowing users to set device aliases and memory
    devices are fragile when it comes to aliases we have to make sure
    they won't change during migration. Other devices should be fine.
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit e2797e3256cbfd43904a4edc3adc949b0bcdd342
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Wed Oct 18 17:46:18 2017 +0200

    conf: Validate user supplied aliases
    
    They have to be unique within the domain. As usual, backwards
    compatibility takes its price. In this particular situation we
    have a device that is represented twice in a domain and so is its
    alias.
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit c14f1ed20647f2c6d0ae14bf8c50234217d2a57b
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Wed Oct 18 14:59:01 2017 +0200

    conf: Parse user supplied aliases
    
    If driver that is calling the parse supports user supplied
    aliases, they can be parsed even for inactive XMLs. However, to
    avoid any clashes with aliases that libvirt generates, the user
    ones have to have "ua-" prefix.
    
    Note, that some drivers don't have notion of device aliases at
    all. Also, in order to support user supplied aliases some extra
    checks need to be done (e.g. during hotplug). Therefore we can't
    just enable this feature for all the drivers. Thus we need a flag
    that drivers set to tell parsing code that they can handle user
    supplied device aliases.
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit ad30f069d108c9e6f30c2aec227d609df3b4e9af
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Fri Oct 20 13:24:41 2017 +0200

    qemu_alias: Be more tolerant if alias don't follow our format
    
    When assigning alias to a device we usually iterate over other
    devices of its kind trying to find next index. We do this by
    stripping down the prefix and then parsing number at the end,
    Usually, if the prefix doesn't match the one we are expecting, we
    just continue with next iteration. Except for couple of
    functions: qemuGetNextChrDevIndex(),
    qemuAssignDeviceRedirdevAlias() and qemuAssignDeviceShmemAlias().
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

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

 


Rackspace

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