From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f42.google.com ([209.85.160.42]:38434 "EHLO mail-pl0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750763AbeDLL5y (ORCPT ); Thu, 12 Apr 2018 07:57:54 -0400 Received: by mail-pl0-f42.google.com with SMTP id c7-v6so3756535plr.5 for ; Thu, 12 Apr 2018 04:57:54 -0700 (PDT) Date: Thu, 12 Apr 2018 17:27:46 +0530 In-Reply-To: <20180412100341.GA9929@sirena.org.uk> References: <0D4A6CC8-6DBA-4F80-AD0C-3EAF5D445CA9@gmail.com> <20180412100341.GA9929@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: v3.18.104 build: 10 failures 1 warnings (v3.18.104) To: Mark Brown CC: kernel-build-reports@lists.linaro.org, linaro-kernel@lists.linaro.org, stable@vger.kernel.org From: Harsh Shandilya Message-ID: Sender: stable-owner@vger.kernel.org List-ID: On 12 April 2018 3:33:41 PM IST, Mark Brown 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=2E15=2E16 hit these as well? > >I'm guessing it's affected all the builds somehow=2E Looks like it, v4=2E15=2E17 is broken just like =2E16 was so clearly the p= roblem has persisted=2E Is it really a disk space issue? --=20 Harsh Shandilya, PRJKT Development LLC