[zorg] r300573 - Remove the ppc64le-clang-lnt buildbot because it continues to be flaky making it hard to listen to/use buildbots effectively due to the noise.

[David Blaikie via llvm-commits]

On Tue, Apr 25, 2017 at 2:11 PM Bill Seurer <seurer at linux.vnet.ibm.com>
wrote:

> On 04/19/2017 09:23 AM, David Blaikie wrote:
> > On Wed, Apr 19, 2017 at 6:24 AM Bill Seurer <seurer at linux.vnet.ibm.com
> > <mailto:seurer at linux.vnet.ibm.com>> wrote:
> >
> >     I had previously spent a good chunk of time tracing
> >     back to the source of other thread-related problems and can adapt the
> >     scripts I used then to investigate whatever you were seeing.  I
> suspect
> >     this might be the same problem as I don't think the previous issues
> >     were ever fixed.
> >
> >
> > Likely was never fixed, by the sounds of it.
>
> I ran 10,000 test iterations on the (then current) revision


Thanks!


> and found
> the following tests were problematic:


>
> FAIL: ThreadSanitizer-powerpc64le :: ignore_lib1.cc
>

I believe this is the one that failed the particular run that I disabled it
on.


> This one fails with some regularity, 48 times in 10,000 runs.
>

I'm surprised it's that low - discussions on IRC seemed to indicate (with
far less data/rigor, to be totally fair) more in the ballpark of 1/10, but
it's good to know it's... somewhat reproducible.


>
>
> FAIL: ThreadSanitizer-powerpc64le :: ignore_lib5.cc
>
> Failed 15 times in 10,000 runs.
>
>
> FAIL: AddressSanitizer-powerpc64le-linux ::
> TestCases/Posix/current_allocated_bytes.cc
>
> Failed 4 times in 10,000 runs
>
>
> TestCases/Posix/current_allocated_bytes.cc
>
> Failed once in 10,000 runs.
>
>
> I looked back at my notes and the previous problem revision for threads
> was r279664.  I don't know if that is the case for these.
> --
>
> -Bill Seurer
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20170425/003e32a9/attachment.html>