[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a145sL=DHiyP39c2FrH9Vh9aZBd7GUs96pWd-93NngQDg@mail.gmail.com>
Date: Thu, 16 Mar 2017 10:59:55 +0100
From: Arnd Bergmann <arnd@...db.de>
To: "kernelci.org bot" <bot@...nelci.org>
Cc: kernel-build-reports@...ts.linaro.org,
Russell King - ARM Linux <linux@...linux.org.uk>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-mips@...ux-mips.org, Ralf Baechle <ralf@...ux-mips.org>,
James Hogan <james.hogan@...tec.com>,
linux-media@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: mainline build: 208 builds: 0 failed, 208 passed, 422 warnings (v4.11-rc2-164-gdefc7d752265)
On Wed, Mar 15, 2017 at 9:02 PM, Arnd Bergmann <arnd@...db.de> wrote:
> On Wed, Mar 15, 2017 at 6:53 PM, kernelci.org bot <bot@...nelci.org> wrote:
>>
>> mainline build: 208 builds: 0 failed, 208 passed, 422 warnings (v4.11-rc2-164-gdefc7d752265)
>
> The last build failure in mainline is gone now, though I don't know
> what fixed it.
> Let's hope this doesn't come back as the cause was apparently a race condition
> in Kbuild that might have stopped triggering.
Now the failure in x86_64 allmodconfig+CONFIG_OF=n is back, which makes it
particularly hard to bisect as the problem only shows up sometimes.
Arnd
Powered by blists - more mailing lists