Skip to content
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

Enforce timeouts for reading rustc version. #1071

Merged
merged 1 commit into from
Apr 19, 2017

Conversation

lifthrasiir
Copy link
Contributor

Some rustc versions (1.3.0 through 1.10.0 if my analysis is correct) are no longer working in recent macOS Sierra, in that they do not produce a correct output nor do not properly terminate in a timely
manner (e.g. loops indefinitely).

Having them in the current toolchain makes rustup update or (sometimes) rustup show unresponsive, so a timeout of one second has been added to correctly show that they are no longer working.

Fixes #766.

Some rustc versions (1.3.0 through 1.10.0 if my analysis is correct)
are no longer working in recent macOS Sierra, in that they do not
produce a correct output nor do not properly terminate in a timely
manner (e.g. loops indefinitely).

Having them in the current toolchain makes `rustup update` or
(sometimes) `rustup show` unresponsive, so a timeout of one second has
been added to correctly show that they are no longer working.

Fixes rust-lang#766.
@lifthrasiir
Copy link
Contributor Author

I have no idea why the test fails on Windows... (The comment "TempDir seems to succumb to difficulties removing dirs on windows" is quite suggestive.)

@Diggsey
Copy link
Contributor

Diggsey commented Apr 19, 2017

@bors r+ Thanks! That test has been very flaky recently :(

@bors
Copy link
Contributor

bors commented Apr 19, 2017

📌 Commit 809bff6 has been approved by Diggsey

@bors
Copy link
Contributor

bors commented Apr 19, 2017

⌛ Testing commit 809bff6 with merge 92a8aed...

bors added a commit that referenced this pull request Apr 19, 2017
Enforce timeouts for reading rustc version.

Some rustc versions (1.3.0 through 1.10.0 if my analysis is correct) are no longer working in recent macOS Sierra, in that they do not produce a correct output nor do not properly terminate in a timely
manner (e.g. loops indefinitely).

Having them in the current toolchain makes `rustup update` or (sometimes) `rustup show` unresponsive, so a timeout of one second has been added to correctly show that they are no longer working.

Fixes #766.
@bors
Copy link
Contributor

bors commented Apr 19, 2017

💔 Test failed - status-travis

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.

3 participants