From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [libvirt test] 62763: trouble: broken/fail/pass
Date: Sun, 11 Oct 2015 01:36:09 +0000 [thread overview]
Message-ID: <osstest-62763-mainreport@xen.org> (raw)
flight 62763 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62763/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-vhd 3 host-install(3) broken REGR. vs. 62727
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 3 host-install(3) broken REGR. vs. 62727
test-amd64-amd64-libvirt-xsm 3 host-install(3) broken REGR. vs. 62727
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-raw 9 debian-di-install fail never pass
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 12 migrate-support-check fail never pass
test-amd64-i386-libvirt 12 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-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
version targeted for testing:
libvirt 4f77c48cbaae66f4326a0a2314b9c6b63db82770
baseline version:
libvirt ef4d14a116fabd14d0b806ade46ae02825e275ce
Last test of basis 62727 2015-10-08 10:12:55 Z 2 days
Testing same since 62763 2015-10-09 19:45:47 Z 1 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrea Bolognani <abologna@redhat.com>
John Ferlan <jferlan@redhat.com>
Maxim Nestratov <mnestratov@virtuozzo.com>
Michal Privoznik <mprivozn@redhat.com>
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 broken
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 pass
test-amd64-i386-libvirt-pair pass
test-armhf-armhf-libvirt-qcow2 fail
test-armhf-armhf-libvirt-raw fail
test-amd64-amd64-libvirt-vhd broken
------------------------------------------------------------
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-step test-amd64-amd64-libvirt-vhd host-install(3)
broken-step test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm host-install(3)
broken-step test-amd64-amd64-libvirt-xsm host-install(3)
Not pushing.
------------------------------------------------------------
commit 4f77c48cbaae66f4326a0a2314b9c6b63db82770
Author: Michal Privoznik <mprivozn@redhat.com>
Date: Thu Oct 8 10:17:42 2015 +0200
virJSONValueArraySize: return ssize_t
The internal representation of a JSON array counts the items in
size_t. However, for some reason, when asking for the count it's
reported as int. Firstly, we need the function to return a signed
type as it's returning -1 on an error. But, not every system has
integer the same size as size_t. Therefore, lets return ssize_t.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
commit 6c928996e6fa4b080e1b93f89831fabf16e71543
Author: Andrea Bolognani <abologna@redhat.com>
Date: Fri Oct 9 11:20:06 2015 +0200
src: Remove $(builddir) usage
Commit 4e8032272f1704f7 used $(builddir) in the header search
path to fix a build issue; however, $(builddir) is not defined
by old autoconf versions such as the one available in CentOS 5,
resulting in the following error:
cc1: error: /util: No such file or directory
make[3]: *** [libvirt_driver_la-fdstream.lo] Error 1
Since $(builddir) is defined to always be '.', just use that
value directly instead.
commit 4e8032272f1704f72feafa359fa51870f73ae265
Author: Andrea Bolognani <abologna@redhat.com>
Date: Thu Oct 8 08:35:29 2015 +0200
src: Include $(builddir)/util in the header search path
Since a9fe620372144db, we are generating virkeymaps.h at build
time; however, we are not including $(builddir)/util in the
header search path, so when doing a VPATH build the compiler
is unable to locate the file.
make[2]: Entering directory
`/home/jenkins/libvirt/systems/libvirt-fedora-20/build/src'
GEN util/virkeymaps.h
...
CC util/libvirt_util_la-virkeycode.lo
CC util/libvirt_util_la-virkeyfile.lo
CC util/libvirt_util_la-virlockspace.lo
CC util/libvirt_util_la-virlog.lo
../../src/util/virkeycode.c:27:24: fatal error: virkeymaps.h: No such file or directory
#include "virkeymaps.h"
^
compilation terminated.
commit 04a39574a8c064c330ced881378715f9606b3f5e
Author: Maxim Nestratov <mnestratov@virtuozzo.com>
Date: Wed Oct 7 13:05:00 2015 +0300
vz: cleanup
Remove unused definitions, functions and structure fields.
Signed-off-by: Maxim Nestratov <mnestratov@virtuozzo.com>
commit 4ee3d4c28545cf81c1ac772801fab0332c6555cf
Author: John Ferlan <jferlan@redhat.com>
Date: Mon Oct 5 09:53:02 2015 -0400
storage: Perform some cleanup of calls
Cleanup calls to virStorageBackendCopyToFD a bit.
Signed-off-by: John Ferlan <jferlan@redhat.com>
reply other threads:[~2015-10-11 1:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=osstest-62763-mainreport@xen.org \
--to=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.