-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
cargo update
#120454
cargo update
#120454
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging. Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
This comment has been minimized.
This comment has been minimized.
d2aabfc
to
f80a7ad
Compare
Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
This comment has been minimized.
This comment has been minimized.
We should run a perf build before merging (but looks like too early for that to be possible). |
f80a7ad
to
145045f
Compare
This comment has been minimized.
This comment has been minimized.
Investigating the above issue, it looks like |
145045f
to
2d164da
Compare
I think that is an intentional consequence of dtolnay/thiserror#248 (subsequently ported to proc-macro2). We don't want these crates using any unstable functionality when used as a rustc dependency, regardless of whether it might work. |
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
`cargo update` Run `cargo update`, with some pinning and fixes necessitated by that. This *should* unblock rust-lang#112865 There's a couple of places where I only pinned a dependency in one location - this seems like a bit of a hack, but better than duplicating the FIXME across all `Cargo.toml` where a dependency is introduced. cc `@Nilstrieb`
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (af2531d): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 662.476s -> 667.297s (0.73%) |
https://github.com/indexmap-rs/indexmap/blob/2.2.1/RELEASES.md
|
f1a77fc
to
9b73db3
Compare
@bors r=Nilstrieb |
`cargo update` Run `cargo update`, with some pinning and fixes necessitated by that. This *should* unblock rust-lang#112865 There's a couple of places where I only pinned a dependency in one location - this seems like a bit of a hack, but better than duplicating the FIXME across all `Cargo.toml` where a dependency is introduced. cc `@Nilstrieb`
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (cc1c099): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 630.069s -> 632.386s (0.37%) |
Improvements and regressions balances themselves out. There are some small binary size regressions though. |
I did a quick analysis - some std dependencies were updated |
Oh, sorry, I missed that. Ok, not much we can do about that. @rustbot label: +perf-regression-triaged |
Thank you very much for getting this through! |
Run
cargo update
, with some pinning and fixes necessitated by that. This should unblock #112865There's a couple of places where I only pinned a dependency in one location - this seems like a bit of a hack, but better than duplicating the FIXME across all
Cargo.toml
where a dependency is introduced.cc @Nilstrieb