-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Bump the version number to 1.90.0 #142792
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
Conversation
@bors r+ p=1 rollup=never |
Bump the version number to 1.90.0 Part of the release process. This PR must not be rolled up. r? cuviper
💔 Test failed - checks-actions |
@rust-lang/cargo it looks like a couple of your tests are not prepared for the actual 1.90?
|
Two tests were using `.rust_version("1.90.0")` for a "newer" Rust, but this failed in rust-lang/rust#142792 for the start of the *real* 1.90.0. Let's bump that to 1.999.0 so we won't have to deal with it for a while.
Two tests were using `.rust_version("1.90.0")` for a "newer" Rust, but this failed in rust-lang/rust#142792 for the start of the *real* 1.90.0. Let's bump that to 1.999.0 so we won't have to deal with it for a while.
Update is up at #142898 |
The Cargo PR merged @bors retry |
☀️ Test successful - checks-actions |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 22be76b (parent) -> ae2fc97 (this PR) Test differencesShow 1 test diffStage 2
Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard ae2fc9722f08ef131407c1dc8057768868f65e8e --output-dir test-dashboard And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
Part of the release process. This PR must not be rolled up.
r? cuviper