-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Add example for std::thread::sleep
.
#34406
Conversation
Thanks! @bors: r+ rollup |
📌 Commit 0183f7f has been approved by |
⌛ Testing commit 0183f7f with merge 56854cb... |
💔 Test failed - auto-linux-cross-opt |
@bors: retry On Wed, Jun 22, 2016 at 9:50 AM, bors [email protected] wrote:
|
⌛ Testing commit 0183f7f with merge 31b6756... |
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
Failure looks legit. But why? |
Good question. I tested it locally and it worked just fine. |
Maybe ">=" instead of ">"? |
Updated to |
@bors: r+ rollup |
📌 Commit bbc33ac has been approved by |
⌛ Testing commit bbc33ac with merge f33dd35... |
💔 Test failed - auto-mac-64-opt |
@bors: retry On Thu, Jun 23, 2016 at 4:11 PM, bors [email protected] wrote:
|
Is there a Windows bug with |
Add example for `std::thread::sleep`. None
⌛ Testing commit bbc33ac with merge cd0b94a... |
💔 Test failed - auto-win-msvc-64-opt |
Add example for `std::thread::sleep`. None
We've discussed this a few times before, but could tests that purposefully block for a long time be tagged with |
@alexcrichton Sure, I can do that, but should there be any concern about the test failing on the Windows builders? |
Nah it's probably just spurious. Most assertions about intervals slept or things like that end up failing eventually. Time's weird. |
Updated to use |
Add example for `std::thread::sleep`. None
Add example for `std::thread::sleep`. None
No description provided.