[llvm-dev] greendragon build noisy due to mmap_stress.cc

Dmitry Vyukov via llvm-dev llvm-dev at lists.llvm.org
Wed Jan 13 02:22:07 PST 2016


Hi,

The test fails without output. So it either SIGSEGVs or OOM-killed. SIGSEGV
can happen if mmap/pthread_create fail (probably with ENOMEM); or on first
access to allocated memory if system allows overcommit.
I've added error checking to the test:
http://llvm.org/viewvc/llvm-project/compiler-rt/trunk/test/tsan/mmap_stress.cc?r1=257585&r2=257584&pathrev=257585
Let's see if any of these show up in output.





On Wed, Jan 13, 2016 at 12:23 AM, Chris Matthews <chris.matthews at apple.com>
wrote:

> I’m running this on green-dragon-03 which is running OSX 10.10.5.
>
> /Users/buildslave/jenkins/sharedspace/clang-stage1-cmake-RA_workspace\@2/clang-build/bin/clang++
> ../llvm/projects/compiler-rt/test/tsan/mmap_stress.cc -lpthread
> while true; do for((i=0;i<10;i++)); do ./a.out || echo
> ===============FAILED================ & done ; wait; done
>
> Seems like it is getting about 225 runs a minute, so it will take about 8
> hours to complete 100k runs.
>
> On Jan 12, 2016, at 1:28 PM, Tobias Grosser via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> On 01/12/2016 10:26 PM, Kostya Serebryany wrote:
>
> Hi Tobias,
>
> What machine is that?
> We have seen this and similar tests be flaky on older Linux kernels due
> to kernel bug(s).
> May I ask you to run the same test (just built with clang) on the same
> machine for ~100000 times and see if it ever crashes?
>
> clang++ ~/llvm/projects/compiler-rt/test/tsan/mmap_stress.cc -lpthread
> while true; do for((i=0;i<10;i++)); do ./a.out || echo
> ===============FAILED================ & done ; wait; done
>
>
> Add Michael again (who might have access to this Machine).
>
> Tobias
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160113/bd937663/attachment.html>


More information about the llvm-dev mailing list