From: xen.org <Ian.Jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [libvirt test] 33157: regressions - trouble: blocked/fail/pass/preparing/queued
Date: Tue, 6 Jan 2015 14:02:33 +0000 [thread overview]
Message-ID: <osstest-33157-mainreport@xen.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3107 bytes --]
flight 33157 libvirt running [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33157/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt <none executed> queued
test-amd64-i386-libvirt <none executed> queued
test-amd64-amd64-libvirt <none executed> queued
build-armhf-libvirt 5 libvirt-build fail REGR. vs. 32648
build-i386-libvirt 5 libvirt-build fail REGR. vs. 32648
build-amd64 2 hosts-allocate running [st=running!]
build-amd64-pvops 2 hosts-allocate running [st=running!]
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 1 build-check(1) blocked n/a
version targeted for testing:
libvirt 18ec863d19bdaf517e26642f794b7ee4d1d2c53f
baseline version:
libvirt 2360fe5d24175835d3f5fd1c7e8e6e13addab629
------------------------------------------------------------
People who touched revisions under test:
Cedric Bosdonnat <cbosdonnat@suse.com>
Chunyan Liu <cyliu@suse.com>
Cédric Bosdonnat <cbosdonnat@suse.com>
Daniel P. Berrange <berrange@redhat.com>
Eric Blake <eblake@redhat.com>
Jim Fehlig <jfehlig@suse.com>
Kiarie Kahurani <davidkiarie4@gmail.com>
Luyao Huang <lhuang@redhat.com>
Nehal J Wani <nehaljw.kkd1@gmail.com>
Pavel Hrdina <phrdina@redhat.com>
------------------------------------------------------------
jobs:
build-amd64 preparing
build-armhf pass
build-i386 pass
build-amd64-libvirt queued
build-armhf-libvirt fail
build-i386-libvirt fail
build-amd64-pvops preparing
build-armhf-pvops pass
build-i386-pvops pass
test-amd64-amd64-libvirt queued
test-armhf-armhf-libvirt blocked
test-amd64-i386-libvirt queued
------------------------------------------------------------
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
broken-job build-amd64-libvirt queued
broken-job test-amd64-i386-libvirt queued
broken-job test-amd64-amd64-libvirt queued
broken build-amd64 hosts-allocate running
broken build-amd64-pvops hosts-allocate running
Not pushing.
(No revision log; it would be 377 lines long.)
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2015-01-06 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 14:02 xen.org [this message]
2015-01-08 16:37 ` [libvirt test] 33157: regressions - trouble: blocked/fail/pass/preparing/queued Jim Fehlig
2015-01-08 16:45 ` Ian Campbell
2015-01-08 17:16 ` Jim Fehlig
2015-01-08 21:56 ` Jim Fehlig
2015-01-09 5:59 ` Jim Fehlig
2015-01-09 9:27 ` Ian Campbell
2015-01-09 16:59 ` Dario Faggioli
2015-01-09 17:55 ` Jim Fehlig
2015-01-19 17:00 ` Ian Campbell
2015-01-19 17:42 ` Ian Jackson
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-33157-mainreport@xen.org \
--to=ian.jackson@eu.citrix.com \
--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.