llvm dev - Sep 2015 - buildbot failure in LLVM on clang-cmake-thumbv7-a15-full-sh

This buildbot looks like it's been failing since Friday - does anyone
know/own/care about it?

---------- Forwarded message ----------
From: <llvm.buildmaster at lab.llvm.org>
Date: Mon, Sep 28, 2015 at 7:29 PM
Subject: buildbot failure in LLVM on clang-cmake-thumbv7-a15-full-sh
To: Adrian Prantl <aprantl at apple.com>, Cameron Esfahani <dirty at
apple.com>,
Chris Bieneman <beanz at apple.com>, David Blaikie <dblaikie at
gmail.com>,
Evgeniy Stepanov <eugeni.stepanov at gmail.com>, Matthias Braun <
matze at braunis.de>, Reid Kleckner <rnk at google.com>
Cc: gkistanova at gmail.com


The Buildbot has detected a new failure on builder
clang-cmake-thumbv7-a15-full-sh while building compiler-rt.
Full details are available at:

http://lab.llvm.org:8011/builders/clang-cmake-thumbv7-a15-full-sh/builds/2418

Buildbot URL: http://lab.llvm.org:8011/

Buildslave for this Build: linaro-chrome-05

Build Reason: scheduler
Build Source Stamp: [branch trunk] 248769
Blamelist: adrian,cbieneman,dblaikie,dirty,eugenis,matze,rnk

BUILD FAILED: failed ninja check 2

sincerely,
 -The Buildbot
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20150929/3fe97b7c/attachment.html>

On 29 September 2015 at 18:22, David Blaikie <dblaikie at gmail.com>
wrote:
> This buildbot looks like it's been failing since Friday - does anyone
> know/own/care about it?
Yes, we're looking into it.

As you probably noticed, debugging ARM buildbots are not easy, not
fast. Reverting commits at random also don't help with the problem,
and bisecting can take days, if not weeks. So the one week rule to
disable bots is too harsh on those bots.

Also, please know that I do care a lot about *all* ARM bots (including
AArch64) and I do check them multiple times a day, so if they're red,
I'm definitely aware and trying to fix it.

cheers,
--renato

On Tue, Sep 29, 2015 at 10:38 AM, Renato Golin <renato.golin at
linaro.org>
wrote:
> On 29 September 2015 at 18:22, David Blaikie <dblaikie at gmail.com>
wrote:
> > This buildbot looks like it's been failing since Friday - does
anyone
> > know/own/care about it?
>
> Yes, we're looking into it.
>
> As you probably noticed, debugging ARM buildbots are not easy, not
> fast. Reverting commits at random also don't help with the problem,
> and bisecting can take days, if not weeks. So the one week rule to
> disable bots is too harsh on those bots.
>
Is it? While it's failing, the buildbot doesn't seem to be any use to
the
community at large - it's essentially the buildbot owners problem at that
point and probably shouldn't be engaging with the community until it's
green again, I think?

Is the buildbot useful to you during this time? Or are you debugging
elsewhere/privately?

If the buildbot is useful to you, but not the community at large - perhaps
we could get in the habit of moving it into a "no email" pool whenever
a
failure occurs, until it can be cleared up. (hopefully this pool is clearly
distinguished from the rest of the buildbots in the waterfall/grid view -
because it'd be helpful to be able to look at an easily distinguished
subset of the waterfall/grid and see the bots that are expected to be green
for any developer there)

> Also, please know that I do care a lot about *all* ARM bots (including
> AArch64) and I do check them multiple times a day, so if they're red,
> I'm definitely aware and trying to fix it.
>
> cheers,
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20150929/e82954fc/attachment.html>