New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Libcxx test case failures on darwin (10.6): tor.pass, eval.pass, sleep_for.pass #20557
Comments
assigned to @mclow |
Interesting; I'm not seeing those failures in my nightly runs. |
This is just wrong; please disregard. |
Are you running with a freshly built dylib? If I run the tests with the libc++.dylib that Apple ships as part of 10.9, then (at least the first two tests) will fail. P.S. For some reason, I cannot connect to lab.llvm.org:8013 |
I have added some logs that might be useful from a failing build. These bots are running 10.6. |
Ah, that's the key. Doug Gregor wrote (back in 2011, on the cfe-developers list):
And Howard Hinnant wrote (in the same thread in 2011):
[ The thread is was titled "libc++ on Mac OS X 10.6" and started on Oct 9, 2011 ] Why are you running 10.6 on this bot? |
This bot is very old. Even though it has not been officially supported, the bot has been green and finding occasional bugs. If this bug is 10.6 specific, the bot could be taken off line. |
I'm willing to try to figure out what's going on here; but if it's just a problem on 10.6, I'm going to give it a lower priority than other bugs. |
That sounds great. Thanks! |
All of these bugs were fixed by David Majnemer!
All of these tests pass against the OS X 10.12 system library but not on 10.11. |
Extended Description
The following tests have been failing on Darwin of a while now:
Failing Tests (3):
libc++ :: numerics/rand/rand.device/ctor.pass.cpp
libc++ :: numerics/rand/rand.device/eval.pass.cpp
libc++ :: thread/thread.threads/thread.thread.this/sleep_for.pass.cpp
The most recent results can be found here:
http://lab.llvm.org:8013/builders/libcxx_clang-x86_64-darwin11-RA?numbuilds=50
The text was updated successfully, but these errors were encountered: