Flaky buildbot clang-x86_64-linux-selfhost-abi-test

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Flaky buildbot clang-x86_64-linux-selfhost-abi-test

Paweł Bylica
This bot seems flaky too. In the last 100 builds there were 11 failures because on of these test had been failed:

FAIL: SanitizerCommon-tsan::signal_segv_handler.cc
FAIL: SanitizerCommon-msan::signal_segv_handler.cc
FAIL: SanitizerCommon-lsan::signal_segv_handler.cc

There were also 5 testing timeouts:

[325/325] Running all regression tests
command timed out: 1200 seconds without output, attempting to kill

- PB

On Wed, Jun 24, 2015 at 4:18 PM <[hidden email]> wrote:
The Buildbot has detected a new failure on builder clang-x86_64-linux-selfhost-abi-test while building llvm.
Full details are available at:
 http://lab.llvm.org:8011/builders/clang-x86_64-linux-selfhost-abi-test/builds/5893

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

Buildslave for this Build: as-bldslv8

Build Reason: scheduler
Build Source Stamp: [branch trunk] 240540
Blamelist: chfast,dsanders

BUILD FAILED: failed ninja check 1

sincerely,
 -The Buildbot




_______________________________________________
LLVM Developers mailing list
[hidden email]         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Reply | Threaded
Open this post in threaded view
|

Re: Flaky buildbot clang-x86_64-linux-selfhost-abi-test

Evgeniy Stepanov
Thanks for bringing this up. We've seen these tests misbehave under
load on sanitizer bots, but not in the last few weeks, and we could
never reproduce it locally. I'll disable the test for now.

Btw, we've also seen this test survive whatever buildbot does in the
case of a step timeout and consuming the CPU cycles forever after
that. Please check the bot for runaway processes.

Sorry about that.


On Thu, Jun 25, 2015 at 5:33 AM, Paweł Bylica <[hidden email]> wrote:

> This bot seems flaky too. In the last 100 builds there were 11 failures
> because on of these test had been failed:
>
> FAIL: SanitizerCommon-tsan::signal_segv_handler.cc
> FAIL: SanitizerCommon-msan::signal_segv_handler.cc
> FAIL: SanitizerCommon-lsan::signal_segv_handler.cc
>
> There were also 5 testing timeouts:
>
> [325/325] Running all regression tests
> command timed out: 1200 seconds without output, attempting to kill
>
> - PB
>
> On Wed, Jun 24, 2015 at 4:18 PM <[hidden email]> wrote:
>>
>> The Buildbot has detected a new failure on builder
>> clang-x86_64-linux-selfhost-abi-test while building llvm.
>> Full details are available at:
>>
>> http://lab.llvm.org:8011/builders/clang-x86_64-linux-selfhost-abi-test/builds/5893
>>
>> Buildbot URL: http://lab.llvm.org:8011/
>>
>> Buildslave for this Build: as-bldslv8
>>
>> Build Reason: scheduler
>> Build Source Stamp: [branch trunk] 240540
>> Blamelist: chfast,dsanders
>>
>> BUILD FAILED: failed ninja check 1
>>
>> sincerely,
>>  -The Buildbot
>>
>>
>>
>
> _______________________________________________
> LLVM Developers mailing list
> [hidden email]         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>

_______________________________________________
LLVM Developers mailing list
[hidden email]         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev