Dmitri Gribenko via llvm-dev
2016-Jan-28 07:20 UTC
[llvm-dev] Some ASan and TSan tests go into an infinite loop on Debian/sid x86_64
Hi, I was just building the top-of-trunk of LLVM/Clang/compiler-rt on Debian/sid x86_64 (with gcc (Debian 5.3.1-7) 5.3.1 20160121) and for me Asan-x86_64-inline-Test/AddressSanitizer.ManyThreadsTest does not finish running: Note: Google Test filter = AddressSanitizer.ManyThreadsTest [==========] Running 1 test from 1 test case. [----------] Global test environment set-up. [----------] 1 test from AddressSanitizer [ RUN ] AddressSanitizer.ManyThreadsTest <just keeps going for minutes> Same for 'ThreadSanitizer :: mmap_stress.cc', but it doesn't produce any output. The tests seem to be multithreaded, so I want to mention that this is an 18-core VM. Maybe the tests are not scaling well? Is this a known issue? Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/
Adhemerval Zanella via llvm-dev
2016-Jan-28 12:56 UTC
[llvm-dev] Some ASan and TSan tests go into an infinite loop on Debian/sid x86_64
On 28-01-2016 05:20, Dmitri Gribenko via llvm-dev wrote:> Hi, > > I was just building the top-of-trunk of LLVM/Clang/compiler-rt on > Debian/sid x86_64 (with gcc (Debian 5.3.1-7) 5.3.1 20160121) and for > me Asan-x86_64-inline-Test/AddressSanitizer.ManyThreadsTest does not > finish running: > > Note: Google Test filter = AddressSanitizer.ManyThreadsTest > [==========] Running 1 test from 1 test case. > [----------] Global test environment set-up. > [----------] 1 test from AddressSanitizer > [ RUN ] AddressSanitizer.ManyThreadsTest > <just keeps going for minutes> > > Same for 'ThreadSanitizer :: mmap_stress.cc', but it doesn't produce any output. > > The tests seem to be multithreaded, so I want to mention that this is > an 18-core VM. Maybe the tests are not scaling well? > > Is this a known issue? > > Dmitri >We noted on AArch64 buildbot constantly [1] so we disabled it on aarch64 for further investigation (I haven't check it yet). Failing on x86_64 makes me believe this is not an architecture specific issue. [1] https://llvm.org/bugs/show_bug.cgi?id=24389
Alexander Potapenko via llvm-dev
2016-Jan-28 13:49 UTC
[llvm-dev] Some ASan and TSan tests go into an infinite loop on Debian/sid x86_64
Have you tried attaching gdb to the running test and collecting the stack trace? On Thu, Jan 28, 2016 at 8:20 AM, Dmitri Gribenko via llvm-dev <llvm-dev at lists.llvm.org> wrote:> Hi, > > I was just building the top-of-trunk of LLVM/Clang/compiler-rt on > Debian/sid x86_64 (with gcc (Debian 5.3.1-7) 5.3.1 20160121) and for > me Asan-x86_64-inline-Test/AddressSanitizer.ManyThreadsTest does not > finish running: > > Note: Google Test filter = AddressSanitizer.ManyThreadsTest > [==========] Running 1 test from 1 test case. > [----------] Global test environment set-up. > [----------] 1 test from AddressSanitizer > [ RUN ] AddressSanitizer.ManyThreadsTest > <just keeps going for minutes> > > Same for 'ThreadSanitizer :: mmap_stress.cc', but it doesn't produce any output. > > The tests seem to be multithreaded, so I want to mention that this is > an 18-core VM. Maybe the tests are not scaling well? > > Is this a known issue? > > Dmitri > > -- > main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if > (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/ > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-- Alexander Potapenko Software Engineer Google Germany GmbH Erika-Mann-Straße, 33 80636 München Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Diese E-Mail ist vertraulich. Wenn Sie nicht der richtige Adressat sind, leiten Sie diese bitte nicht weiter, informieren Sie den Absender und löschen Sie die E-Mail und alle Anhänge. Vielen Dank. This e-mail is confidential. If you are not the right addressee please do not forward it, please inform the sender, and please erase this e-mail including any attachments. Thanks.