-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
run some tests with minimal-versions on CI #5856
Conversation
r? @matklad (rust_highfive has picked a reviewer for you, use r? to override) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, if it passes 😄
Travis:
|
Thanks! I think we can probably afford to do this on Travis, but I don't think we have enough capacity to do this on AppVeyor :( (we're already getting pretty backed up by just adding |
I got |
I have a guess! Rustc cache works by saving a I guess that serde_json changed serialization of long integers some time in the past: you can't save integers with more than 53 as ints, b/c JavaScript does not have integers, and that explains where the strings might come from. I've done zero real investigation though, but let's try to pin-up serde-[json] version? |
Now appear is complaining failures: But I will not be able too work on OSS stuff for the next week. |
Back and rebased. This time it is: appveyor:
travis:
Ideays? |
The
Line 16 in 6a7672e
|
1.28 does (rust-lang/rust#49546). Shouldn't that CI setup be upgrade to Rust 1.28 instead? |
tests/testsuite/check.rs
Outdated
@@ -724,6 +724,10 @@ fn check_artifacts() { | |||
|
|||
#[test] | |||
fn short_message_format() { | |||
if !is_nightly() { | |||
// This can be removed once 1.30 is stable (rustdoc --error-format stabilized). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The message here is wrong. This relies on rustc --error-format
which is stable as of 1.28, but we're (currently) using 1.27.2.
I propose we upgrade to that CI setup to 1.28 and remove this guard.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. Can we also remove this from doc::short_message_format
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That one not till 1.30.
In other news, this went ✅❗️❗️ |
With green tests, this may be good to land? My main concern would be about CI time on AppVeyor (40m minimum) which is a bit excessive, could we perhaps stick to |
I am just commiting a back out on AppVeyor. The inspiration for doing this work was all the libgit2 windows bugs around |
Gah bummer :( We can try to be vigilant about those sorts of fixes for now, and otherwise if we feel like we have more appveyor capacity in the future we can always reenable! @bors: r+ |
📋 Looks like this PR is still in progress, ignoring approval. Hint: Remove [WIP] from this PR's title when it is ready for review. |
@bors: r=alexcrichton |
📌 Commit 620d5cc has been approved by |
run some tests with minimal-versions on CI In #5757 we discovered that sum test don't pass with minimal-versions, and so only added CI for `cargo check`. This PR is to see if that is still needed, and if it is then which test rely on upstream bugfix.
☀️ Test successful - status-appveyor, status-travis |
In #5757 we discovered that sum test don't pass with minimal-versions, and so only added CI for
cargo check
. This PR is to see if that is still needed, and if it is then which test rely on upstream bugfix.