search for: deep_thread_stack

...e asan tests, but I'm not 100% certain and unfortunately don't have time to dive into this one. Would you mind taking a quick scan of the logs below and letting me know if anything stands out to you. Failing Tests (14): AddressSanitizer :: Linux/unpoison_tls.cc AddressSanitizer :: deep_thread_stack.cc AddressSanitizer-Unit :: Asan-i386-Test/AddressSanitizer.ManyThreadsTest AddressSanitizer-Unit :: Asan-i386-Test/AddressSanitizer.PthreadExitTest AddressSanitizer-Unit :: Asan-i386-Test/AddressSanitizer.ThreadNamesTest AddressSanitizer-Unit :: Asan-i386-Test/AddressSanitizer.Thre...

On Thu, May 30, 2013 at 10:05 PM, Greg Fitzgerald <garious at gmail.com> wrote: > The sanitizer common and asan that mention 'thread' are failing for me > this morning. How are your bots looking? Last good commit here was > 512c616cacf70ca029a2bf719a482b902f3687cd. > Hm, our bots seem to be green. Could you refer to guilty svn revision? > > > You could try

The sanitizer common and asan that mention 'thread' are failing for me this morning. How are your bots looking? Last good commit here was 512c616cacf70ca029a2bf719a482b902f3687cd. > You could try preprocessing your report with perl or sed to fix paths > to your binaries. It would be great to have an option for that in > asan_symbolize.py. > > As for addr2line, we just

Dear testers, 5.0.0-rc1 has just been tagged. Please build, test and upload binaries to the sftp. Let me know if there are any issues. I'll upload sources, docs, and your binaries to the pre-release website once they're ready. Thanks, Hans

...Cases/Posix/asan-sigbus.cpp (2998 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/Posix/asan-symbolize-sanity-test.cc (3000 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/Posix/closed-fds.cc (3001 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/Posix/deep_thread_stack.cc (3005 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/Posix/fread_fwrite.cc (3007 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/Posix/interception-in-shared-lib-test.cc (3019 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/Posix/shared-lib-test.c...

Hi, The 6.0.1-rc2 release has been tagged. Testers may begin testing and reporting results. -Tom

Hi, I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do so please try to do this before Friday, because I would like to tag 5.0.2-final then. As a reminder to users and developers, May 18 is the deadline for submitting merge requests for 6.0.1, so there is still time to get bug fixes

...nterface.HandleNoReturnTest AddressSanitizer-i386-freebsd :: TestCases/Posix/asan-sigbus.cpp AddressSanitizer-i386-freebsd :: TestCases/Posix/asan-symbolize-sanity-test.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/closed-fds.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/deep_thread_stack.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/fread_fwrite.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/interception-in-shared-lib-test.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/invalid-pointer-pairs-threads.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/...

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>

On 31 Jul 2017, at 19:26, Hans Wennborg <hans at chromium.org> wrote: > > On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric <dimitry at andric.com> wrote: >> On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev <cfe-dev at lists.llvm.org> wrote: >>> >>> 5.0.0-rc1 has just been tagged. >>> >>> Please build, test and upload binaries