[Xen-devel] [libvirt test] 29560: trouble: blocked/broken/fail/pass

[xen.org <Ian.Jackson@xxxxxxxxxxxxx>]

flight 29560 libvirt real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/29560/

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64                   3 host-install(3)         broken REGR. vs. 29539
 build-i386                    3 host-install(3)         broken REGR. vs. 29539
 build-i386-pvops              3 host-install(3)         broken REGR. vs. 29539

Tests which did not succeed, but are not blocking:
 test-amd64-i386-libvirt       1 build-check(1)               blocked  n/a
 test-armhf-armhf-libvirt      9 guest-start                  fail   never pass
 test-amd64-amd64-libvirt      1 build-check(1)               blocked  n/a
 build-i386-libvirt            1 build-check(1)               blocked  n/a
 build-amd64-libvirt           1 build-check(1)               blocked  n/a

version targeted for testing:
 libvirt              221b1828f9bf9d1d59d2d4b318249de9f7ec7bb8
baseline version:
 libvirt              24c55ee04d2055a65d6292f23a400a75fb719493

------------------------------------------------------------
People who touched revisions under test:
  Cédric Bosdonnat <cbosdonnat@xxxxxxxx>
  Eric Blake <eblake@xxxxxxxxxx>
  Roman Bogorodskiy <bogorodskiy@xxxxxxxxx>
------------------------------------------------------------

jobs:
 build-amd64                                                  broken
 build-armhf                                                  pass
 build-i386                                                   broken
 build-amd64-libvirt                                          blocked
 build-armhf-libvirt                                          pass
 build-i386-libvirt                                           blocked
 build-amd64-pvops                                            pass
 build-armhf-pvops                                            pass
 build-i386-pvops                                             broken
 test-amd64-amd64-libvirt                                     blocked
 test-armhf-armhf-libvirt                                     fail
 test-amd64-i386-libvirt                                      blocked


------------------------------------------------------------
sg-report-flight on osstest.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images

Logs, config files, etc. are available at
    http://www.chiark.greenend.org.uk/~xensrcts/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
commit 221b1828f9bf9d1d59d2d4b318249de9f7ec7bb8
Author: Roman Bogorodskiy <bogorodskiy@xxxxxxxxx>
Date:   Thu Jul 24 19:52:11 2014 +0400

    docs: bhyve: document recent changes

     - mention that one disk and one network limitation
       is no longer current for 1.2.6 and newer
     - add 'cdrom' device to the sample domain XML

commit cfb16b8ed7bf5a082566e36b658945028cdffc59
Author: Eric Blake <eblake@xxxxxxxxxx>
Date:   Wed Jun 18 17:16:27 2014 -0600

    blockcommit: turn on active commit

    With this in place, I can (finally!) now do:

    virsh blockcommit $dom vda --shallow --verbose --pivot

    and watch qemu shorten the backing chain by one, followed by
    libvirt automatically updating the dumpxml output, effectively
    undoing the work of virsh snapshot-commit --no-metadata --disk-only.
    Commit is SOOOO much faster than blockpull, when I'm still fairly
    close in time to when the temporary qcow2 wrapper file was created
    via a snapshot operation!

    * src/qemu/qemu_driver.c (qemuDomainBlockCommit): Implement live
    commit.

    Signed-off-by: Eric Blake <eblake@xxxxxxxxxx>

commit 232a31bea3bfde7118bbb0c6594949b62b9bd2a0
Author: Eric Blake <eblake@xxxxxxxxxx>
Date:   Mon Jul 28 21:46:44 2014 -0600

    blockcommit: track job type in xml

    A future patch is going to wire up qemu active block commit jobs;
    but as they have similar events and are canceled/pivoted in the
    same way as block copy jobs, it is easiest to track all bookkeeping
    for the commit job by reusing the <mirror> element.  This patch
    adds domain XML to track which job was responsible for creating a
    mirroring situation, and adds a job='copy' attribute to all
    existing uses of <mirror>.  Along the way, it also massages the
    qemu monitor backend to read the new field in order to generate
    the correct type of libvirt job (even though it requires a
    future patch to actually cause a qemu event that can be reported
    as an active commit).  It also prepares to update persistent XML
    to match changes made to live XML when a copy completes.

    * docs/schemas/domaincommon.rng: Enhance schema.
    * docs/formatdomain.html.in: Document it.
    * src/conf/domain_conf.h (_virDomainDiskDef): Add a field.
    * src/conf/domain_conf.c (virDomainBlockJobType): String conversion.
    (virDomainDiskDefParseXML): Parse job type.
    (virDomainDiskDefFormat): Output job type.
    * src/qemu/qemu_process.c (qemuProcessHandleBlockJob): Distinguish
    active from regular commit.
    * src/qemu/qemu_driver.c (qemuDomainBlockCopy): Set job type.
    (qemuDomainBlockPivot, qemuDomainBlockJobImpl): Clean up job type
    on completion.
    * tests/qemuxml2xmloutdata/qemuxml2xmlout-disk-mirror-old.xml:
    Update tests.
    * tests/qemuxml2argvdata/qemuxml2argv-disk-mirror.xml: Likewise.
    * tests/qemuxml2argvdata/qemuxml2argv-disk-active-commit.xml: New
    file.
    * tests/qemuxml2xmltest.c (mymain): Drive new test.

    Signed-off-by: Eric Blake <eblake@xxxxxxxxxx>

commit 251d75a86324b8de09a88c9289229ca88cf58892
Author: Cédric Bosdonnat <cbosdonnat@xxxxxxxx>
Date:   Wed Jul 30 11:20:59 2014 +0200

    Domain config: write <features/> if some capabilities are set.

    If all features are set to default (including the capabilities policy),
    but some capabilities are toggled, we need to output the <features>
    element when formatting the config.

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