search for: ra_check

Hi, one of the greendragon bots is flaky due to mmap_stress.cc in compiler-rt. In the last two days this bot failed three times (and recovered) due to thhe mmap_stress.cc test in compiler-rt: http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9557/testReport/ http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9551/testReport/ http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9532/testReport/ Dmitry Vyukov, you seem to have committed this test case back in March. Could you possibly have a look? CCed Michael wh...

On 02/02/2016 06:25 PM, Kuba Brecka via llvm-dev wrote: > Done in r259529. I unfortunately just got another failure, so this is clearly not darwin only or even low-noise on none-darwin platforms: http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9965/ I very much appreciate that people are investigating this issue, but it would be really nice to meanwhile disable this test case. Best, Tobias

...test, which explains why it fails on some builds. Can we change the test to keep its output? Will it just be blank anyways? > On Jan 20, 2016, at 1:23 PM, Kostya Serebryany <kcc at google.com> wrote: > > The test fails again: http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9739/testReport/junit/ThreadSanitizer/ThreadSanitizer/mmap_stress_cc/ <http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9739/testReport/junit/ThreadSanitizer/ThreadSanitizer/mmap_stress_cc/> > But unfortunately lit does not provide the original log, so we still don't know...

...d : 1 > // tid : kTidBits > // is_atomic : 1 > // is_read : 1 > // size_log : 2 > // addr0 : 3 > // epoch : kClkBits +Nico pointed to another failure: http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9782/testReport/ThreadSanitizer/ThreadSanitizer/mmap_stress_cc/

These ran to completion without error. :( > On Jan 12, 2016, at 3:23 PM, 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

It is expected and not unusual to need to update the lit test in such case. I'd need to see exactly which test breaks and how to know though. Best, -- Mehdi 2017-09-18 13:17 GMT-07:00 Johan Engelen <jbc.engelen at gmail.com>: > The fix (https://reviews.llvm.org/D37961) does not work. From what I > have learned thusfar, the module identifier is used as filename sometimes >

...un this test manually (with exact same build command line) a few thousand times? I continue to suspect a kernel bug. > > On Jan 20, 2016, at 1:23 PM, Kostya Serebryany <kcc at google.com> wrote: > > The test fails again: > http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9739/testReport/junit/ThreadSanitizer/ThreadSanitizer/mmap_stress_cc/ > But unfortunately lit does not provide the original log, so we still don't > know why... > > On Wed, Jan 13, 2016 at 1:11 PM, Chris Matthews <chris.matthews at apple.com> > wrote: > >> These ra...

...configurations. http://lab.llvm.org:8080/green/view/Clang/job/clang-stage1-configure-RA_build/ <http://lab.llvm.org:8080/green/view/Clang/job/clang-stage1-configure-RA_build/> We also have a buildbot running cmake tests on OS X: http://lab.llvm.org:8080/green/view/All/job/clang-stage1-cmake-RA_check/ <http://lab.llvm.org:8080/green/view/All/job/clang-stage1-cmake-RA_check/> > > Anna. > >> On Feb 17, 2015, at 10:54 AM, Kostya Serebryany <kcc at google.com <mailto:kcc at google.com>> wrote: >> >> +1 (in case you still need mine) >> >>...

...kernel bug. >>> >>>> >>>>> On Jan 20, 2016, at 1:23 PM, Kostya Serebryany <kcc at google.com <mailto:kcc at google.com>> wrote: >>>>> >>>>> The test fails again: http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9739/testReport/junit/ThreadSanitizer/ThreadSanitizer/mmap_stress_cc/ <http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9739/testReport/junit/ThreadSanitizer/ThreadSanitizer/mmap_stress_cc/> >>>>> But unfortunately lit does not provide the original log, so we stil...

...ontinue to suspect a kernel bug. >> >>> >>>> On Jan 20, 2016, at 1:23 PM, Kostya Serebryany <kcc at google.com <mailto:kcc at google.com>> wrote: >>>> >>>> The test fails again: http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9739/testReport/junit/ThreadSanitizer/ThreadSanitizer/mmap_stress_cc/ <http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_check/9739/testReport/junit/ThreadSanitizer/ThreadSanitizer/mmap_stress_cc/> >>>> But unfortunately lit does not provide the original log, so we still do...

Unfortunately, we do rely on the Autotools to build for darwin. The lack of proper testing is very unfortunate. In the future, we will either drop the dependency on Makefile/autoconf build or add the support for sanitizer testing. Anna. > On Feb 17, 2015, at 10:54 AM, Kostya Serebryany <kcc at google.com> wrote: > > +1 (in case you still need mine) > > On Thu, Feb 12,