search for: threadpooltest

...fe-dev < cfe-dev at lists.llvm.org> wrote: > SuSE Linux Enterprise Server 11SP3 x86_64 > > Looks like I see several failures that weren't in 3.7.1. Is there any way > to tell whether these are regressions vs new-to-3.8.0-but-failing? The > MSan ones were in 3.7.1 but the ThreadPoolTest and the libc++ errors were > not in 3.7.1. > > All of the libc++ failures seem like non-issues and should be in 3.7.1. Did you change or upgrade your platform or libc version? I'm not sure about the libc++abi error though. > ~~~~~~~~~~~~~~~~ > Failing Tests (27): > LLVM...

...g is attached. Failing Tests (94): LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncIntInt LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncVoidBool LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestSerialization LLVM-Unit :: Support/SupportTests/ThreadPoolTest.Async LLVM-Unit :: Support/SupportTests/ThreadPoolTest.AsyncBarrier LLVM-Unit :: Support/SupportTests/ThreadPoolTest.AsyncBarrierArgs LLVM-Unit :: Support/SupportTests/ThreadPoolTest.GetFuture LLVM-Unit :: Support/SupportTests/ThreadPoolTest.PoolDestruction All of these ^^ failed w...

(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

...>> >>> SuSE Linux Enterprise Server 11SP3 x86_64 >>> >>> Looks like I see several failures that weren't in 3.7.1. Is there any >>> way to tell whether these are regressions vs new-to-3.8.0-but-failing? The >>> MSan ones were in 3.7.1 but the ThreadPoolTest and the libc++ errors were >>> not in 3.7.1. >>> >>> >> All of the libc++ failures seem like non-issues and should be in 3.7.1. >> Did you change or upgrade your platform or libc version? I'm not sure >> about the libc++abi error though. >> &g...

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

...ise Server 11SP3 x86_64 > >>>> > >>>> Looks like I see several failures that weren't in 3.7.1. Is there any > >>>> way to tell whether these are regressions vs > new-to-3.8.0-but-failing? The > >>>> MSan ones were in 3.7.1 but the ThreadPoolTest and the libc++ errors > were > >>>> not in 3.7.1. > >>>> > >>> > >>> All of the libc++ failures seem like non-issues and should be in 3.7.1. > >>> Did you change or upgrade your platform or libc version? I'm not sure > abo...