search for: fgetgrent_r

...M-Unit :: Support/SupportTests/ThreadPoolTest.PoolDestruction > MemorySanitizer :: Linux/obstack.cc > MemorySanitizer :: Linux/process_vm_readv.cc > MemorySanitizer :: fork.cc > MemorySanitizer :: iconv.cc > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.fgetgrent_r > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getgrent > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getgrent_r > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getpwent > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getpwe...

...ionMarkers.cpp LLVM :: tools/llvm-cov/showTemplateInstantiations.cpp LLVM :: tools/llvm-cov/universal-binary.c LLVM :: tools/llvm-cov/warnings.h These ^^ fail with "std::future_error / No associated state" as well. MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.fgetgrent_r MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getgrent MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getgrent_r These don't confess why they failed in the log. MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostbyname_r_bad_host_name This one fa...

(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

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

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