From: Mark Brown <broonie@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v4.15.10 build: 2 failures 0 warnings (v4.15.10)
Date: Sun, 18 Mar 2018 17:52:16 -0700 [thread overview]
Message-ID: <20180319005216.GX2186@sirena.org.uk> (raw)
In-Reply-To: <20180316080231.GA13244@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 273 bytes --]
On Fri, Mar 16, 2018 at 09:02:31AM +0100, Greg KH wrote:
> On Thu, Mar 15, 2018 at 06:46:06PM +0000, Build bot for Mark Brown wrote:
> > Passed: 7 / 9 ( 77.78 %)
> > Failed: 2 / 9 ( 22.22 %)
> What is the failure?
Looks like the build server ran out of space.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-03-19 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 18:46 v4.15.10 build: 2 failures 0 warnings (v4.15.10) Build bot for Mark Brown
2018-03-16 8:02 ` Greg KH
2018-03-19 0:52 ` Mark Brown [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=20180319005216.GX2186@sirena.org.uk \
--to=broonie@kernel.org \
--cc=greg@kroah.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox