-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
sched::test::dont_starve_1 deadlocks with valgrind and on bsd #9407
Comments
Relevant commit is c767643 Yay for relativity! or something like that. |
It was attempted to only run this test when not running on valgrind, but @thestinger noticed that it still failed on bsd, so it was completely removed as a test (the code's still there) in #9412 |
This is because the buildbot configuration sets RUST_RT_TEST_THREADS=1 when valgrinding and this test depends on that value being >1. |
@brson: any idea why it also deadlocks on the BSD bot? I added a workaround for valgrind but it wasn't enough |
This updates a number of ignore-test tests, and removes a few completely outdated tests due to the feature being tested no longer being supported. This brings a number of bench/shootout tests up to date so they're compiling again. I make no claims to the performance of these benchmarks, it's just nice to not have bitrotted code. Closes #2604 Closes #9407
I think this test only works when you have more than one physical/logical core.
The text was updated successfully, but these errors were encountered: