-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Bring test of nightly in line with tests #4010
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
@bors: r+ |
📌 Commit e0e4a1d has been approved by |
It looks like homu isn't processing approved PRs for cargo or rustup-rs. Do you know why that is @Mark-Simulacrum? |
@bors: retry |
@bors: r+ |
💡 This pull request was already approved, no need to approve it again. |
📌 Commit e0e4a1d has been approved by |
e0e4a1d
to
213a2bf
Compare
@bors: r+ |
📌 Commit 213a2bf has been approved by |
@bors: retry |
@alexcrichton it doesn't look like the issue is the approval, but rather that homu isn't taking jobs off of the queue. Jobs in the |
…richton Bring test of nightly in line with tests #4000 passes `-Zincremental` to `rustc` only on nightly, but uses a different mechanism for detecting nightly than [cargotest does](https://github.com/rust-lang/cargo/blob/9bf9bddd9297cfb5098be6146d85be551c6d4eff/tests/cargotest/lib.rs#L37). This PR brings the two in line, which should hopefully fix the build failure observed in rust-lang/rust#41830 (comment).
Also relies on rust-lang/cargo#4010
☀️ Test successful - status-appveyor, status-travis |
#4000 passes
-Zincremental
torustc
only on nightly, but uses a different mechanism for detecting nightly than cargotest does. This PR brings the two in line, which should hopefully fix the build failure observed in rust-lang/rust#41830 (comment).