search for: threaddescriptorsize

...-with-call-Test/MemorySanitizer.getgrent_r > MemorySanitizer-Unit :: > Msan-x86_64-with-call-Test/MemorySanitizer.getpwent > MemorySanitizer-Unit :: > Msan-x86_64-with-call-Test/MemorySanitizer.getpwent_r > SanitizerCommon-Unit :: > Sanitizer-x86_64-Test/SanitizerLinux.ThreadDescriptorSize > ThreadSanitizer :: Linux/mutex_robust.cc > ThreadSanitizer :: Linux/mutex_robust2.cc > ThreadSanitizer :: thread_name2.cc > libc++ :: std/depr/depr.c.headers/uchar_h.pass.cpp > This is caused because the system does not provide a uchar.h header. > libc++ :...

...overage_shared.test Profile-x86_64 :: Linux/coverage_test.cpp Profile-x86_64 :: Linux/extern_template.test Profile-x86_64 :: Linux/instrprof-comdat.test Profile-x86_64 :: instrprof-visibility.cpp ^^ std::future_error SanitizerCommon-Unit :: Sanitizer-x86_64-Test/SanitizerLinux.ThreadDescriptorSize /tmp/llvm/utils/release/rc2/llvm.src/projects/compiler-rt/lib/sanitizer_common/tests/sanitizer_linux_test.cc:230: Failure Value of: ThreadDescriptorSize() Actual: 2288 Expected: (uptr)result Which is: 2304 Scudo :: alignment.cpp Scudo :: double-free.cpp Scudo :: malloc.cpp Scud...

...it :: Asan-i386-Test/AddressSanitizer.ThreadedTest AddressSanitizer-Unit :: Asan-i386-Test/AddressSanitizerInterface.ManyThreadsWithStatsStressTest SanitizerCommon-Unit :: Sanitizer-i386-Test/SanitizerCommon.ThreadStackTlsWorker SanitizerCommon-Unit :: Sanitizer-i386-Test/SanitizerLinux.ThreadDescriptorSize Here's the log. Anything stand out to you? -- Testing: 15209 tests, 4 threads -- Testing: FAIL: AddressSanitizer :: Linux/unpoison_tls.cc (19 of 15209) ******************** TEST 'AddressSanitizer :: Linux/unpoison_tls.cc' FAILED ******************** Script: -- /local/mnt/workspace/d...

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

Hi, I just tagged 3.9.1-rc2, so testing can begin. There was a bug found in -rc1 before I could send out a release announcement, so I decided to merge the fix and tag -rc2 to save some testing cycles. We can always use more testers, so if you are interested in helping, let me know. Thanks, Tom

(cc'ing non-legacy llvm-dev this time; apologies if you get this twice. Please don't reply-all to the first one.) On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg <hans at chromium.org> wrote: > Dear testers, > > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at > r258223. (It took a little longer than I'd planned, sorry about that.) > > There

On Wed, Jul 13, 2016 at 04:48:51PM +0200, Sedat Dilek via llvm-dev wrote: > [ CCed all people who were involved in this thread ] > > Hi Tom, > > personally, I am interested to test the prebuilt-toolchains for > Ubuntu/xenial alias 16.04 LTS and Debian/Jessie v8.5.0 AMD64. > The available toolchains are incomplete and thus useless. > > Just as a fact: There is still no

Hi, There was one problem in -rc1, so we had to do another release candidate. -rc2 has now been tagged and is ready for testing. -Tom