From: Ian Campbell <ian.campbell@citrix.com>
To: "xen.org" <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-unstable test] 29899: regressions - FAIL
Date: Thu, 21 Aug 2014 20:44:48 +0100 [thread overview]
Message-ID: <1408650288.7363.8.camel@citrix.com> (raw)
In-Reply-To: <osstest-29899-mainreport@xen.org>
On Thu, 2014-08-21 at 19:48 +0100, xen.org wrote:
> flight 29899 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/29899/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-armhf 5 xen-build fail REGR. vs. 29680
> build-armhf-pvops 5 kernel-build fail REGR. vs. 29680
The ARM build cluster's NBD server (which serves the nbd root to the
boards) was incorrectly configured and had filled its / partition, which
had a knock on effect of the build boards themselves. We think this is
now fixed...
Ian.
prev parent reply other threads:[~2014-08-21 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 18:48 [xen-unstable test] 29899: regressions - FAIL xen.org
2014-08-21 19:44 ` Ian Campbell [this message]
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=1408650288.7363.8.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).