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

[Xen-devel] [libvirt test] 25910: tolerable FAIL

flight 25910 libvirt real [real]

Failures :-/ but no regressions.

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

version targeted for testing:
 libvirt              a4209f53795290ff9f2173092800eb3f767fff3e
baseline version:
 libvirt              6077be466efcc2d57679e59db8a4b1626ed0757c

People who touched revisions under test:
  Eric Blake <eblake@xxxxxxxxxx>
  Jiri Denemark <jdenemar@xxxxxxxxxx>
  Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx>

 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-armhf-libvirt                                          fail    
 build-i386-libvirt                                           pass    
 build-amd64-oldkern                                          pass    
 build-i386-oldkern                                           pass    
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-libvirt                                     fail    
 test-armhf-armhf-libvirt                                     blocked 
 test-amd64-i386-libvirt                                      fail    

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

Test harness code can be found at

Pushing revision :

+ branch=libvirt
+ revision=a4209f53795290ff9f2173092800eb3f767fff3e
+ . cri-lock-repos
++ . cri-common
+++ . cri-getconfig
+++ umask 002
+++ getconfig Repos
+++ perl -e '
                use Osstest;
                print $c{"Repos"} or die $!;
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ '[' x '!=' x/export/home/osstest/repos/lock ']'
++ OSSTEST_REPOS_LOCK_LOCKED=/export/home/osstest/repos/lock
++ exec with-lock-ex -w /export/home/osstest/repos/lock ./ap-push libvirt 
+ branch=libvirt
+ revision=a4209f53795290ff9f2173092800eb3f767fff3e
+ . cri-lock-repos
++ . cri-common
+++ . cri-getconfig
+++ umask 002
+++ getconfig Repos
+++ perl -e '
                use Osstest;
                print $c{"Repos"} or die $!;
++ repos=/export/home/osstest/repos
++ repos_lock=/export/home/osstest/repos/lock
++ '[' x/export/home/osstest/repos/lock '!=' x/export/home/osstest/repos/lock 
+ . cri-common
++ . cri-getconfig
++ umask 002
+ select_xenbranch
+ case "$branch" in
+ tree=libvirt
+ xenbranch=xen-unstable
+ '[' xlibvirt = xlinux ']'
+ linuxbranch=
+ : tested/2.6.39.x
+ . ap-common
++ : osstest@xxxxxxxxxxxxxxxxxxxxx
++ : git://xenbits.xen.org/xen.git
++ : osstest@xxxxxxxxxxxxxxxxxxxxx:/home/xen/git/xen.git
++ : git://xenbits.xen.org/staging/qemu-xen-unstable.git
++ : git://git.kernel.org
++ : git://git.kernel.org/pub/scm/linux/kernel/git
++ : git
++ : git://libvirt.org/libvirt.git
++ : osstest@xxxxxxxxxxxxxxxxxxxxx:/home/xen/git/libvirt.git
++ : git://xenbits.xen.org/libvirt.git
++ : git
++ : git://git.sv.gnu.org/gnulib.git
++ : git
++ : git://xenbits.xen.org/osstest/linux-firmware.git
++ : osstest@xxxxxxxxxxxxxxxxxxxxx:/home/osstest/ext/linux-firmware.git
++ : git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
++ : osstest@xxxxxxxxxxxxxxxxxxxxx:/home/xen/git/linux-pvops.git
++ : git://xenbits.xen.org/linux-pvops.git
++ : tested/linux-3.4
++ : tested/linux-arm-xen
++ '[' xgit://xenbits.xen.org/linux-pvops.git = x ']'
++ '[' x = x ']'
++ : git://xenbits.xen.org/linux-pvops.git
++ : tested/linux-arm-xen
++ : git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
++ : tested/2.6.39.x
++ : daily-cron.libvirt
++ : daily-cron.libvirt
++ : daily-cron.libvirt
++ : daily-cron.libvirt
++ : http://hg.uk.xensource.com/carbon/trunk/linux-2.6.27
++ : git://xenbits.xen.org/staging/qemu-upstream-unstable.git
++ : daily-cron.libvirt
+ TREE_LINUX=osstest@xxxxxxxxxxxxxxxxxxxxx:/home/xen/git/linux-pvops.git
+ TREE_XEN=osstest@xxxxxxxxxxxxxxxxxxxxx:/home/xen/git/xen.git
+ TREE_LIBVIRT=osstest@xxxxxxxxxxxxxxxxxxxxx:/home/xen/git/libvirt.git
+ info_linux_tree libvirt
+ case $1 in
+ return 1
./ap-push: line 83: syntax error near unexpected token `)'
commit a4209f53795290ff9f2173092800eb3f767fff3e
Author: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx>
Date:   Thu Apr 17 06:30:08 2014 -0400

    qemu: Unlock the NWFilter update lock by leaving via the cleanup label
    Fix a locking problem by leaving the function via the cleanup label.
    Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx>

commit 4090e15399672c74227dcebc19d91b151d5d049f
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Wed Apr 9 12:17:39 2014 -0400

    storage: netfs: Handle backend errors
    Commit id '18642d10' caused a virt-test regression for NFS backend
    storage error path checks when running the command:
        'virsh find-storage-pool-sources-as netfs Unknown  '
    when the host did not have Gluster installed. Prior to the commit,
    the test would fail with the error:
        error: internal error: Child process (/usr/sbin/showmount --no-headers
        --exports Unknown) unexpected exit status 1: clnt_create: RPC: Unknown 
    After the commit, the error would be ignored, the call would succeed,
    and an empty list of pool sources returned. This was tucked into the
    commit message as an expected outcome.
    When the target host does not have a GLUSTER_CLI this is a regression
    over the previous release. Furthermore, even if Gluster CLI was present,
    but had a failure to get devices, the API would return a failure even if
    the NFS backend had found devices.
    Modify the logic to return failure when the NFS backend check fails and
    there's no GLUSTER_CLI or when both backend checks fail.
    If either returns success and GLUSTER_CLI is defined, then fetch and return
    a list of source devices even if it's empty

commit 8fb446754deda2f9d953eeb854a5aa050c8599f5
Author: Eric Blake <eblake@xxxxxxxxxx>
Date:   Mon Apr 14 16:54:19 2014 -0600

    conf: fix omission of <driver> in domain dumpxml
    I noticed that depending on the <driver> attributes the user passed
    in, the output may omit the <driver> element altogether.  For example,
    the rerror_policy has had this problem since commit 4bb4109 in Oct
    2011.  But in adding testsuite coverage to expose it, I found another
    problem: the C code is just fine without a driver name, but the
    XML validator required either a name or a cache mode.
    * src/conf/domain_conf.c (virDomainDiskDefFormat): Update
    * docs/schemas/domaincommon.rng (diskDriver): Simplify.
    * tests/qemuxml2argvdata/qemuxml2argv-disk-drive-copy-on-read.xml:
    * tests/qemuxml2argvdata/qemuxml2argv-disk-drive-copy-on-read.args:
    New files.
    * tests/qemuxml2argvdata/qemuxml2argv-disk-drive-discard.xml:
    Enhance test.
    * tests/qemuxml2xmloutdata/qemuxml2xmlout-disk-drive-discard.xml:
    * tests/qemuxml2argvtest.c (mymain): New test.
    * tests/qemuxml2xmltest.c (mymain): Likewise.
    Signed-off-by: Eric Blake <eblake@xxxxxxxxxx>
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit fec1a93927c860934b4e983dce4ecbbe44485a93
Author: Eric Blake <eblake@xxxxxxxxxx>
Date:   Mon Apr 14 16:54:16 2014 -0600

    conf: split <disk> schema into more pieces
    To make <disk> schema more maintainable and to allow for moving the
    pieces to a common file in the future. It relies on the ability to
    override definitions as part of an include, set up in the previous
    The diff is a bit hard to read, because it mixes reindentation
    with refactoring; 'git diff -b --patience' may help.
    * docs/schemas/domaincommon.rng (disk): Refactor into pieces.
    (diskSource, diskSourceFile, diskSourceBlock, diskSourceDir)
    (diskSourceVolume: New defines.
    (diskSourceNetwork): Revise scope.
    * docs/schemas/domainsnapshot.rng (disksnapshot): Adjust.
    * tests/domainsnapshotxml2xmlin/disk-seclabel-invalid.xml,
    tests/domainsnapshotxml2xmlin/disk-network-seclabel-invalid.xml: New
    tests to check seclabel is forbidden in domain snapshot by schema.
    Signed-off-by: Eric Blake <eblake@xxxxxxxxxx>
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit 369cdfa8f54c9848cc44327fb9b2bb67e01def8a
Author: Eric Blake <eblake@xxxxxxxxxx>
Date:   Mon Apr 14 16:54:15 2014 -0600

    conf: set up for per-grammar overrides in schemas
    This patch is my first experience playing with nested grammars,
    as documented in http://relaxng.org/tutorial-20011203.html#IDA3PZR.
    I plan on doing more overrides in order to make the RelaxNG
    grammar mirror the C code refactoring into a common
    virStorageSource, but where different clients of that source do
    not support the same subset of functionality.  By starting with
    something fairly easy to validate, I can make sure my later
    patches will be possible.
    This patch adds a use of the no-op <ref
    name='sourceStartupPolicy'/> to the disksnapshot definition, so
    that the snapshot version of a type='file' <source> more closely
    resembles the version in domaincommon.  A future patch will merge
    the two files into using a common define, but this patch is
    sufficient for testing that adding <source
    startupPolicy='optional'/> in any of the
    tests/domainsnapshotxml2xmlin/*.xml files still gets rejected
    unless it occurs within the <domain> subelement, because the
    definition of startupPolicy is empty outside of domain.rng.
    * docs/schemas/storagecommon.rng (storageStartupPolicy)
    (storageSourceExtra): Create no-op defaults.
    * docs/schemas/domainsnapshot.rng (domain): Use nested grammar
    to avoid restricting <domain>.
    (storageSourceExtra): Create new override.
    (disksnapshot): Access overrides through common names.
    * docs/schemas/domaincommon.rng (disk): Access overrides through
    common names.
    * docs/schemas/domain.rng (storageStartupPolicy)
    (storageSourceExtra): Create new overrides.
    Signed-off-by: Eric Blake <eblake@xxxxxxxxxx>
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit db7d7c0ee8a1a6db2d81a71e10794bc5c597b301
Author: Eric Blake <eblake@xxxxxxxxxx>
Date:   Mon Apr 14 16:54:14 2014 -0600

    conf: restrict external snapshots to backing store formats
    Domain snapshots should only permit an external snapshot into
    a storage format that permits a backing chain, since the new
    snapshot file necessarily must be backed by the existing file.
    The C code for the qemu driver is a little bit stricter in
    currently enforcing only qcow2 or qed, but at the XML parser
    level, including virt-xml-validate, it is fairly easy to
    enforce that a user can't request a 'raw' external snapshot.
    * docs/schemas/storagecommon.rng (storageFormat): Split out...
    (storageFormatBacking): ...new sublist.
    * docs/schemas/domainsnapshot.rng (disksnapshotdriver): Use new
    * src/util/virstoragefile.h (virStorageFileFormat): Rearrange for
    easier code management.
    * src/util/virstoragefile.c (virStorageFileFormat, fileTypeInfo):
    * src/conf/snapshot_conf.c (virDomainSnapshotDiskDefParseXML): Use
    new marker to limit selection of formats.
    Signed-off-by: Eric Blake <eblake@xxxxxxxxxx>
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit 4f596a070d7e5cb52d7908a03b414617f81fc517
Author: Eric Blake <eblake@xxxxxxxxxx>
Date:   Mon Apr 14 16:54:13 2014 -0600

    conf: move storage formats to common RNG file
    We had incomplete RelaxNG support for storage formats listed
    in virstoragefile.h: commit 027bf2e added 'vdi' but forgot
    to update the <volume> and <domain> xml lists; the <volume>
    list was also missing 'fat' and 'vhd'.  Maintaining two lists
    is a recipe for them getting out of sync, so make the list
    common so that both contexts benefit the next time we add a
    format in a single location.
    * docs/schemas/domaincommon.rng (storageFormat): Move...
    * docs/schemas/storagecommon.rng: ...here, and add vdi.
    * docs/schemas/storagevol.rng (formatfile): Use common list.
    Signed-off-by: Eric Blake <eblake@xxxxxxxxxx>

commit a9efe2d70cd43a5c60163a1873a7adc146e9efaf
Author: Eric Blake <eblake@xxxxxxxxxx>
Date:   Mon Apr 14 16:54:12 2014 -0600

    conf: better <disk> interleaving in schema
    In general, we try to make virt-xml-validate tolerant of input
    elements in any order when possible.  However, as written, the
    RNG grammar did not permit <source> unless there was an explicit
    type= attribute (even though the C code manages just fine by
    defaulting to type='file').  After making the attribute optional
    on the 'file' branch, I noticed that the use of diskspec was now
    redundant with the branch when no <source> was supplied.
    View this patch with 'git diff -b' for a better picture of the
    schema change.
    * docs/schemas/domaincommon.rng (disk): Hoist 'diskspec' out of
    choice, make type='file' default, and still preserve interleave.
    * tests/qemuxml2xmloutdata/qemuxml2xmlout-disk-source-pool.xml:
    * tests/qemuxml2xmloutdata/qemuxml2xmlout-disk-drive-discard.xml:
    New files.
    * tests/qemuxml2argvdata/qemuxml2argv-disk-source-pool.xml:
    * tests/qemuxml2argvdata/qemuxml2argv-disk-drive-discard.xml:
    Reorder XML.
    * tests/qemuxml2xmltest.c (mymain): Cover new files.
    Signed-off-by: Eric Blake <eblake@xxxxxxxxxx>

Xen-devel mailing list



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