Uh oh!
There was an error while loading. Please reload this page.
Bump cargo for rust-lang/cargo#4000 - #41830
Conversation
rust-highfive
commented
May 8, 2017
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
jonhoo
commented
May 8, 2017
@bors: r? @alexcrichton |
alexcrichton
commented
May 8, 2017
@bors: r+ Thanks! |
bors
commented
May 8, 2017
📌 Commit 2827718 has been approved by |
Due to #37107, this keeps being bumped down the homu queue :( |
Mark-Simulacrum
commented
May 9, 2017
@bors p=1 |
bors
commented
May 9, 2017
⌛ Testing commit 2827718 with merge c35b85d... |
bors
commented
May 9, 2017
💔 Test failed - status-travis |
Mark-Simulacrum
commented
May 9, 2017
Legitimate failure, I believe: |
jonhoo
commented
May 9, 2017
I'm quite confused. The same test passes just fine in the cargo repository... r.verbose_version.contains("-nightly") ||
r.verbose_version.contains("-dev")Whereas the cargo PR only checks for |
Ah, looks like I also missed updating the other EDIT: Nope, looks like git is smart enough to keep them the same revision. Well then -- I guess it's probably the version matching then? |
jonhoo
commented
May 9, 2017
It is slightly disturbing that all cargo tests passed in the cargo repo, but then one of them fails here. Suggests a mismatch in the setups that maybe we should look into. @alexcrichton any idea why this might happen? |
alexcrichton
commented
May 9, 2017
Heh I can name a zillion differences between the two, any one of which could cause tests to pass in one location and fail in the other. In any case rust-lang/cargo#4010 should fix this. |
jonhoo
commented
May 9, 2017
Hehe, fair. Well, that's the hope. If that fails I'm not entirely sure what else it could be. Let's wait and see. |
…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).
jonhoo
commented
May 9, 2017
alexcrichton
commented
May 9, 2017
@bors: r+ |
bors
commented
May 9, 2017
📌 Commit 1617eee has been approved by |
bors
commented
May 9, 2017
Bump cargo for rust-lang/cargo#4000rust-lang/cargo#4000 recently landed, which fixes warnings about using `-Z` when `CARGO_INCREMENTAL` is set while running stable/beta builds. As #41751 has now landed, these warnings will turn to errors in the next release, so getting the cargo fix in place is necessary unless we want people confused about why they can no longer compile anything on stable/beta.
bors
commented
May 9, 2017
☀️ Test successful - status-appveyor, status-travis |
rust-lang/cargo#4000 recently landed, which fixes warnings about using
-ZwhenCARGO_INCREMENTALis set while running stable/beta builds. As #41751 has now landed, these warnings will turn to errors in the next release, so getting the cargo fix in place is necessary unless we want people confused about why they can no longer compile anything on stable/beta.