From: Harsh Shandilya <msfjarvis@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v3.18.104 build: 10 failures 1 warnings (v3.18.104)
Date: Thu, 12 Apr 2018 17:27:46 +0530 [thread overview]
Message-ID: <A558488B-2386-4E4D-830D-443CC713FDDB@gmail.com> (raw)
In-Reply-To: <20180412100341.GA9929@sirena.org.uk>
On 12 April 2018 3:33:41 PM IST, Mark Brown <broonie@kernel.org> wrote:
>On Wed, Apr 11, 2018 at 11:54:13PM +0530, Harsh Shandilya wrote:
>
>> These test results look pretty off, the disk space issue from
>v4.15.16 hit these as well?
>
>I'm guessing it's affected all the builds somehow.
Looks like it, v4.15.17 is broken just like .16 was so clearly the problem has persisted. Is it really a disk space issue?
--
Harsh Shandilya, PRJKT Development LLC
next prev parent reply other threads:[~2018-04-12 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 16:12 v3.18.104 build: 10 failures 1 warnings (v3.18.104) Build bot for Mark Brown
2018-04-11 18:24 ` Harsh Shandilya
2018-04-12 10:03 ` Mark Brown
2018-04-12 11:57 ` Harsh Shandilya [this message]
2018-04-12 11:59 ` Mark Brown
2018-04-12 12:07 ` Harsh Shandilya
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=A558488B-2386-4E4D-830D-443CC713FDDB@gmail.com \
--to=msfjarvis@gmail.com \
--cc=broonie@kernel.org \
--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 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.