Skip to content

test: Use Thread::scoped in two more tests #20925

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

Merged
merged 1 commit into from
Jan 11, 2015

Conversation

alexcrichton
Copy link
Member

I saw these hanging on a windows bot, and the previous ones seem to have calmed
down after switching from Thread::spawn to Thread::scoped, so try that here as
well!

I saw these hanging on a windows bot, and the previous ones seem to have calmed
down after switching from Thread::spawn to Thread::scoped, so try that here as
well!
@rust-highfive
Copy link
Contributor

r? @nikomatsakis

(rust_highfive has picked a reviewer for you, use r? to override)

@sfackler
Copy link
Member

Is the theory that bad things happen if the main thread exits before other threads?

@alexcrichton
Copy link
Member Author

Yeah I'm not quite sure what's going on here, but all the tests which hang indefinitely all have some thread which may live past the main thread exiting. Many of them are also related to failure in child threads, but I'm not sure if all of them are.

cc #20704, the previous set of tests

bors added a commit that referenced this pull request Jan 11, 2015
I saw these hanging on a windows bot, and the previous ones seem to have calmed
down after switching from Thread::spawn to Thread::scoped, so try that here as
well!
@bors bors merged commit b8304e5 into rust-lang:master Jan 11, 2015
@alexcrichton alexcrichton deleted the more-flaky-test branch January 20, 2015 06:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants