-
Notifications
You must be signed in to change notification settings - Fork 13.3k
test: Join child threads on windows in tests #25824
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
test: Join child threads on windows in tests #25824
Conversation
Windows tests can often deadlock if a child thread continues after the main thread and then panics, and a `println!` executed in a child thread after the main thread has exited is at risk of panicking.
(rust_highfive has picked a reviewer for you, use r? to override) |
@bors r+ |
📌 Commit 279ec9b has been approved by |
@bors p=1 |
⌛ Testing commit 279ec9b with merge dc4818c... |
💔 Test failed - auto-win-gnu-32-opt |
@bors: retry On Wed, May 27, 2015 at 3:05 PM, bors [email protected] wrote:
|
…r=nikomatsakis Windows tests can often deadlock if a child thread continues after the main thread and then panics, and a `println!` executed in a child thread after the main thread has exited is at risk of panicking.
Windows historically has problems with threads panicking and the main thread exiting at the same time, typically causing deadlocks. In the past (rust-lang#25824) we've joined on threads but this just prevents running the test for now to avoid tampering with the example.
std: Prevent deadlocks in doctests on Windows Windows historically has problems with threads panicking and the main thread exiting at the same time, typically causing deadlocks. In the past (#25824) we've joined on threads but this just prevents running the test for now to avoid tampering with the example.
Windows tests can often deadlock if a child thread continues after the main
thread and then panics, and a
println!
executed in a child thread after themain thread has exited is at risk of panicking.