Update cargo

[weihanglo]

28 commits in 840b83a10fb0e039a83f4d70ad032892c287570a..71eb84f21aef43c07580c6aed6f806a6299f5042
2025-07-30 13:59:19 +0000 to 2025-08-17 17:18:56 +0000

• update tests to match lint message changes from mention lint group in default level lint note #140794 (update tests to match lint message changes from rust-lang/rust#140794 cargo#15849)
• chore: downgrade to [email protected] (chore: downgrade to [email protected] cargo#15851)
• Reorder lto options in profiles.md (Reorder lto options in profiles.md cargo#15841)
• feat(unstable): add -Zbuild-analysis unstable feature (feat(unstable): add -Zbuild-analysis unstable feature cargo#15845)
• refactor(unstable): group stabilized features (refactor(unstable): group stabilized features cargo#15846)
• Fixes error while running the cargo clippy --all-targets -- -D warning (Fixes error while running the cargo clippy --all-targets -- -D warning cargo#15843)
• Clarify that cargo doc --no-deps is cumulative and won’t delete prev (Clarify that cargo doc --no-deps is cumulative and won’t delete prev cargo#15800)
• docs: Formatting and cross-linking to build-dir/target-dir docs (docs: Formatting and cross-linking to build-dir/target-dir docs cargo#15840)
• Stabilize build.build-dir (Stabilize build.build-dir cargo#15833)
• make resolve features public for cargo-as-a-library (make resolve features public for cargo-as-a-library cargo#15835)
• chore(deps): bump slab from 0.4.10 to 0.4.11 (chore(deps): bump slab from 0.4.10 to 0.4.11 cargo#15832)
• chore: remove x86_64-apple-darwin from CI and tests (chore: remove x86_64-apple-darwin from CI and tests cargo#15831)
• chore(deps): update msrv (3 versions) to v1.87 (chore(deps): update msrv (3 versions) to v1.87 cargo#15819)
• perf(package): Always reuse the workspace's target-dir (perf(package): Always reuse the workspace's target-dir cargo#15783)
• More helpful error for invalid cargo-features = [] (More helpful error for invalid cargo-features = [] cargo#15781)
• Add initial integration for --json=timings behing -Zsection-timings (Add initial integration for --json=timings behing -Zsection-timings cargo#15780)
• add is_inherited methods to InheritableDependency and InheritableField (add is_inherited methods to InheritableDependency and InheritableField cargo#15828)
• chore(deps): update compatible (chore(deps): update compatible cargo#15804)
• docs(unstable): Link out to the Plumbing commands effort (docs(unstable): Link out to the Plumbing commands effort cargo#15821)
• chore(deps): update cargo-semver-checks to v0.43.0 (chore(deps): update cargo-semver-checks to v0.43.0 cargo#15825)
• test(build-std): relax the thread name assertion (test(build-std): relax the thread name assertion cargo#15822)
• chore(deps): update msrv (1 version) to v1.89 (chore(deps): update msrv (1 version) to v1.89 cargo#15815)
• Update semver tests for 1.89 (Update semver tests for 1.89 cargo#15816)
• Accessing each build script's OUT_DIR and in the correct order (Accessing each build script's OUT_DIR and in the correct order cargo#15776)
• chore: bump to 0.92.0; update changelog (chore: bump to 0.92.0; update changelog cargo#15807)
• docs: -Zpackage-workspace has been stabilized (docs: -Zpackage-workspace has been stabilized cargo#15808)
• chore(deps): update rust crate cargo_metadata to 0.21.0 (chore(deps): update rust crate cargo_metadata to 0.21.0 cargo#15795)
• docs(build-rs): Fix broken intra-doc links (docs(build-rs): Fix broken intra-doc links cargo#15810)

[rustbot]

Some changes occurred in src/tools/cargo

cc @ehuss

[rustbot]

⚠️ Warning ⚠️

• Some commits in this PR modify submodules.

  If this was not intentional, see I changed a submodule on accident in the rustc dev guide.

[weihanglo]

@bors r+ rollup=never p=1

[bors]

📌 Commit fbcca5f has been approved by weihanglo

It is now in the queue for this repository.

[bors]

⌛ Testing commit fbcca5f with merge 4570ab6...

[bors]

💔 Test failed - checks-actions

[weihanglo]

rust-lang/cargo#15851 should unblock loongarch64.

@bors retry

[weihanglo]

@bors r+ rollup=never p=1

[bors]

📌 Commit 08263c9 has been approved by weihanglo

It is now in the queue for this repository.

[bors]

⌛ Testing commit 08263c9 with merge 689491c...

[bors]

💔 Test failed - checks-actions

[bors]

⌛ Testing commit 08263c9 with merge 6e37e9a...

[Zalathar]

The i686-msvc-1 job seems to be stuck on “wait for Windows disk cleanup to finish”, and hasn't started the actual build. 😕

(I'm assuming that's more CI/runner flakiness, unrelated to any particular changes.)

https://github.com/rust-lang/rust/actions/runs/17030877518

[Zalathar]

Even if this job spontaneously becomes unstuck, it's still not going to finish in under 6 hours. Better to reroll the CI dice now.

@bors retry

[Zalathar]

Failed in rollup: #145552 (comment)

@bors r-
@rustbot blocked (needs #145478)

[Zalathar]

Whoops, didn't mean to do that to this PR.

@bors r=weihanglo

[bors]

📌 Commit 08263c9 has been approved by weihanglo

It is now in the queue for this repository.

[weihanglo]

The i686-msvc-1 job seems to be stuck on “wait for Windows disk cleanup to finish”, and hasn't started the actual build. 😕

(I'm assuming that's more CI/runner flakiness, unrelated to any particular changes.)

rust-lang/rust/actions/runs/17030877518

actions/runner#3792 maybe?

I don't know how self-hosted runners and Actions talk to each other though

[bors]

⌛ Testing commit 08263c9 with merge aaf87a6...

[bors]

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing aaf87a6 to master...

[github-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 239e8b1 (parent) -> aaf87a6 (this PR)

Test differences

Show 10 test diffs

Stage 2

• build_analysis::gated: [missing] -> pass (J0)
• build_analysis::simple: [missing] -> pass (J0)
• build_dir::verify_build_dir_is_disabled_by_feature_flag: pass -> [missing] (J0)
• build_scripts_multiple::build_script_with_conflicts_reverse_sorted: [missing] -> pass (J0)
• cargo_features::feature_syntax: [missing] -> pass (J0)
• cargo_features::wrong_kind_of_feature: [missing] -> pass (J0)
• package::package_should_use_build_cache: [missing] -> pass (J0)

Additionally, 3 doctest diffs were found. These are ignored, as they are noisy.

Job group index

• J0: aarch64-apple, aarch64-gnu, x86_64-gnu-aux, x86_64-msvc-ext1

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard aaf87a6d289053246d19f94fbc9972582816e93d --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

1. dist-apple-various: 5198.4s -> 6812.6s (31.1%)
2. dist-x86_64-apple: 16279.0s -> 12572.4s (-22.8%)
3. x86_64-apple-1: 10500.6s -> 8238.2s (-21.5%)
4. x86_64-apple-2: 6905.2s -> 7703.7s (11.6%)
5. x86_64-msvc-ext2: 6052.5s -> 6627.6s (9.5%)
6. dist-aarch64-msvc: 5842.3s -> 5308.7s (-9.1%)
7. aarch64-msvc-1: 7416.7s -> 6839.8s (-7.8%)
8. x86_64-mingw-2: 8180.2s -> 7556.2s (-7.6%)
9. aarch64-gnu-llvm-19-1: 3291.9s -> 3511.5s (6.7%)
10. x86_64-gnu-llvm-19-2: 5697.1s -> 6076.7s (6.7%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

[rust-timer]

Finished benchmarking commit (aaf87a6): comparison URL.

Overall result: ❌✅ regressions and improvements - please read the text below

Our benchmarks found a performance regression caused by this PR.
This might be an actual regression, but it can also be just noise.

Next Steps:

• If the regression was expected or you think it can be justified,
  please write a comment with sufficient written justification, and add
  @rustbot label: +perf-regression-triaged to it, to mark the regression as triaged.
• If you think that you know of a way to resolve the regression, try to create
  a new PR with a fix for the regression.
• If you do not understand the regression or you think that it is just noise,
  you can ask the @rust-lang/wg-compiler-performance working group for help (members of this group
  were already notified of this PR).

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	1.1%	[1.0%, 1.2%]	2
Regressions ❌ (secondary)	1.1%	[1.1%, 1.1%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.3%	[-0.4%, -0.3%]	7
All ❌✅ (primary)	1.1%	[1.0%, 1.2%]	2

Max RSS (memory usage)

Results (primary -2.9%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-2.9%	[-2.9%, -2.9%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-2.9%	[-2.9%, -2.9%]	1

Cycles

Results (primary 2.3%, secondary 4.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	2.3%	[2.3%, 2.3%]	1
Regressions ❌ (secondary)	11.9%	[11.9%, 11.9%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-3.7%	[-3.7%, -3.7%]	1
All ❌✅ (primary)	2.3%	[2.3%, 2.3%]	1

Binary size

Results (secondary -0.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.0%	[-0.0%, -0.0%]	1
All ❌✅ (primary)	-	-	0

Bootstrap: 470.133s -> 472.035s (0.40%)
Artifact size: 377.59 MiB -> 377.77 MiB (0.05%)

[Mark-Simulacrum]

Hard to be 100% confident given recency, but I'm pretty sure this is just bimodality. Cargo shouldn't have much practical relation to rustc perf anyway, assuming we don't tweak codegen/rustc flags (and I don't see that in the diff above).

[weihanglo]

I didn't see anything outstanding. Could be rust-lang/cargo#15804 that updating some dependencies (like toml?). [email protected] does have a 200+ lines of Cargo.toml, though I am not sure if it really caused the regression: https://docs.rs/crate/syn/2.0.101/source/Cargo.toml.

[Mark-Simulacrum]

We don't measure Cargo's execution, just rustc, so basically nothing at the Cargo level should get reflected (even if it's terrible :)