From: Ian Campbell <ian.campbell@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [osstest test] 60149: regressions - FAIL
Date: Fri, 31 Jul 2015 09:49:30 +0100 [thread overview]
Message-ID: <1438332570.30740.23.camel@citrix.com> (raw)
In-Reply-To: <1438324802.28924.44.camel@citrix.com>
On Fri, 2015-07-31 at 07:40 +0100, Ian Campbell wrote:
> On Fri, 2015-07-31 at 05:01 +0000, osstest service owner wrote:
> > flight 60149 osstest real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/60149/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > build-i386-libvirt 5 libvirt-build fail REGR.
> > vs. 60083
> > build-amd64-libvirt 5 libvirt-build fail REGR.
> > vs. 60083
> > build-armhf-libvirt 5 libvirt-build fail REGR.
> > vs. 60083
>
> Pretest contains the libvirt testing from Wei (ccd)
>
> One of the libvirt self tests failed:
> TEST: virshtest
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 40
> !!!!!!!!!!!! 52 FAIL
> FAIL: virshtest
> [...]
> =======================================
> 1 of 114 tests failed
> (1 test was not run)
> Please report to libvir-list@redhat.com
> =======================================
>
> Which isn't a lot to go on, aside frmo fixing this issue do we need to
> gather more logs?
Shall we drop "ts-libvirt-build: run libvirt test suite" from pretest for
the time being? It seems a bit orthogonal to the rest of the series anyway.
Ian.
next prev parent reply other threads:[~2015-07-31 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <osstest-60149-mainreport@xen.org>
2015-07-31 6:40 ` [osstest test] 60149: regressions - FAIL Ian Campbell
2015-07-31 8:49 ` Ian Campbell [this message]
2015-07-31 8:50 ` Wei Liu
2015-07-31 9:47 ` Ian Campbell
2015-07-31 9:54 ` Ian Campbell
2015-07-31 10:15 ` Ian Campbell
2015-07-31 9:54 ` Wei Liu
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=1438332570.30740.23.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.