-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Weekly cargo update
#112865
Weekly cargo update
#112865
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Mark-Simulacrum (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
@bors r+ rollup=never |
If there perf regression, is it even possible to fast find which crates it is? |
⌛ Testing commit 361e8aa with merge 4e434b4ab0ac776c51107ebb57912446166956fc... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
the cachegrind diff may help |
361e8aa
to
fca6437
Compare
☔ The latest upstream changes (presumably #112884) made this pull request unmergeable. Please resolve the merge conflicts. |
i created #113046 to fix tidy |
fca6437
to
ca8a9ab
Compare
☔ The latest upstream changes (presumably #113256) made this pull request unmergeable. Please resolve the merge conflicts. |
cargo update rust-lang#112865 with the tidy exemptions and tracing and syn 2 not upgraded Additional deps: equivalent: indexmap errno: through rustix errno-dragonfly: errno nu-ansi-term: tracing overload: nu-ansi-term r? Mark-Simulacrum
ca8a9ab
to
7c80079
Compare
@bors r+ rollup=iffy |
FYI, I have a fix for the cc-rs upgrade issue: rust-lang/cc-rs#940 |
8ffd678
to
57bce6a
Compare
`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`
`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`
57bce6a
to
3c7198d
Compare
☔ The latest upstream changes (presumably #120920) made this pull request unmergeable. Please resolve the merge conflicts. |
`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`
`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`
3c7198d
to
9a4a0c0
Compare
☔ The latest upstream changes (presumably #121265) made this pull request unmergeable. Please resolve the merge conflicts. |
9a4a0c0
to
2d6cda4
Compare
☔ The latest upstream changes (presumably #121677) made this pull request unmergeable. Please resolve the merge conflicts. |
Updating ahash v0.8.8 -> v0.8.10 Updating annotate-snippets v0.10.1 -> v0.10.2 Updating anstream v0.6.11 -> v0.6.13 Updating anyhow v1.0.79 -> v1.0.80 Updating bumpalo v3.14.0 -> v3.15.3 Updating clap v4.5.0 -> v4.5.1 Updating clap_builder v4.5.0 -> v4.5.1 Updating clap_complete v4.5.0 -> v4.5.1 Updating crossbeam-channel v0.5.11 -> v0.5.12 Updating darling v0.20.6 -> v0.20.8 Updating darling_core v0.20.6 -> v0.20.8 Updating darling_macro v0.20.6 -> v0.20.8 Updating dlmalloc v0.2.5 -> v0.2.6 Updating indexmap v2.2.3 -> v2.2.5 Updating libloading v0.8.1 -> v0.8.2 Updating log v0.4.20 -> v0.4.21 Updating mio v0.8.10 -> v0.8.11 Updating normpath v1.1.1 -> v1.2.0 Updating openssl v0.10.63 -> v0.10.64 Updating openssl-sys v0.9.99 -> v0.9.101 Updating pest v2.7.7 -> v2.7.8 Updating pest_derive v2.7.7 -> v2.7.8 Updating pest_generator v2.7.7 -> v2.7.8 Updating pest_meta v2.7.7 -> v2.7.8 Updating pkg-config v0.3.29 -> v0.3.30 Updating rayon v1.8.1 -> v1.9.0 Downgrading regex v1.9.4 -> v1.8.4 Updating regex-automata v0.3.7 -> v0.3.9 Updating reqwest v0.11.23 -> v0.11.24 Adding rustls-pemfile v1.0.4 Updating ryu v1.0.16 -> v1.0.17 Updating semver v1.0.21 -> v1.0.22 Updating serde v1.0.196 -> v1.0.197 Updating serde_derive v1.0.196 -> v1.0.197 Updating serde_json v1.0.113 -> v1.0.114 Updating socket2 v0.5.5 -> v0.5.6 Updating syn v2.0.48 -> v2.0.52 Adding sync_wrapper v0.1.2 Updating sysinfo v0.30.5 -> v0.30.6 Updating tempfile v3.10.0 -> v3.10.1 Updating thread_local v1.1.7 -> v1.1.8 Updating unicode-normalization v0.1.22 -> v0.1.23 Updating unicode-script v0.5.5 -> v0.5.6 Updating walkdir v2.4.0 -> v2.5.0 Updating windows-targets v0.52.0 -> v0.52.4 Updating windows_aarch64_gnullvm v0.52.0 -> v0.52.4 Updating windows_aarch64_msvc v0.52.0 -> v0.52.4 Updating windows_i686_gnu v0.52.0 -> v0.52.4 Updating windows_i686_msvc v0.52.0 -> v0.52.4 Updating windows_x86_64_gnu v0.52.0 -> v0.52.4 Updating windows_x86_64_gnullvm v0.52.0 -> v0.52.4 Updating windows_x86_64_msvc v0.52.0 -> v0.52.4
2d6cda4
to
8ef1981
Compare
🤞🏻 |
@bors p=1 conflicty |
☀️ Test successful - checks-actions |
Finished benchmarking commit (da02fff): comparison URL. Overall result: ❌ regressions - 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. 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 sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 654.421s -> 648.592s (-0.89%) |
Looks to be pretty much all in LLVM, as well as a lot of cycles in jemalloc. |
Artifact size saw a nice win. Overall I'm satisfied that given the many deps updated here there's not much more worth investigating. |
Automation to keep dependencies in
Cargo.lock
current.The following is the output from
cargo update
: