search for: future_error

...ncBarrier LLVM-Unit :: Support/SupportTests/ThreadPoolTest.AsyncBarrierArgs LLVM-Unit :: Support/SupportTests/ThreadPoolTest.GetFuture LLVM-Unit :: Support/SupportTests/ThreadPoolTest.PoolDestruction All of these ^^ failed with: terminate called after throwing an instance of 'std::future_error' what(): No associated state AddressSanitizer-x86_64-linux :: TestCases/Linux/interface_symbols_linux.c This fails with "sed: invalid option -- 'E'". The OS X manpage ( https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/sed.1.ht...

It looks like there are errors in the buildbot runs with std::future_error when executing lot of tests, probably we can disable it for now to make the buildbot clean ? http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-ubuntu-13.04/builds/26755/steps/test/logs/stdio has more information. Shankar Easwaran -- Qualcomm Innovation Center, Inc. is a member of Code A...

...on my machine. Can you? I can only speculate a cause. But I'll try to disable the feature to see if buildbot will get back to green. On Thu, Feb 26, 2015 at 9:08 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > It looks like there are errors in the buildbot runs with std::future_error > when executing lot of tests, probably we can disable it for now to make the > buildbot clean ? > > http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_ > 64-ubuntu-13.04/builds/26755/steps/test/logs/stdio has more information. > > Shankar Easwaran > > -- > Qualcomm...

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