Update cargo submodule

[weihanglo]

19 commits in 24bb93c388fb8c211a37986539f24a819dc669d3..966f94733bbc94ca51ff9f1e4c49ad250ebbdc50
2025-09-10 23:16:07 +0000 to 2025-09-16 17:24:45 +0000

• fix(frontmatter): Improve error quality (fix(frontmatter): Improve error quality cargo#15972)
• fix: wrong variable name in documentation (fix: wrong variable name in documentation cargo#15968)
• Add "Optimizing Build Performance" section to the Cargo book (Add "Optimizing Build Performance" section to the Cargo book cargo#15924)
• Remove extra apostrophe in environment-variables.md (Remove extra apostrophe in environment-variables.md cargo#15963)
• Clarify warning for using features or default-features in patch (Clarify warning for using features or default-features in patch cargo#15953)
• fix(frontmatter): Try alternative len code fences (fix(frontmatter): Try alternative len code fences cargo#15952)
• feat(cli): Allow completions for third-party subcommand names (feat(cli): Allow completions for third-party subcommand names cargo#15961)
• docs(index): Clarify what we mean by omitting features (docs(index): Clarify what we mean by omitting features cargo#15957)
• fix(future): Report all content as a single Report (fix(future): Report all content as a single Report cargo#15943)
• fix(complete): Show local crates/features over other members (fix(complete): Show local crates/features over other members  cargo#15956)
• docs(resolver): Describe the role of the lockfile (docs(resolver): Describe the role of the lockfile  cargo#15958)
• chore: Skip check-version-bump ci job in forks (chore: Skip check-version-bump ci job in forks cargo#15959)
• Eliminate the last three "did you mean" warning phrasings (Eliminate the last three "did you mean" warning phrasings cargo#15356)
• fix(info): Suggest a more universal cargo tree command (fix(info): Suggest a more universal cargo tree command cargo#15954)
• feat(cli): Use ellipses when truncating progress (feat(cli): Use ellipses when truncating progress cargo#15955)
• feat(completer): Added completion for --features flag (feat(completer): Added completion for --features flag cargo#15309)
• fix(publish): Switch the 'ctrl-c on wait' line to a help message (fix(publish): Switch the 'ctrl-c on wait' line to a help message cargo#15942)
• docs: move docs building process to contributor guide (docs: move docs building process to contributor guide cargo#15854)
• fix(manifest): Show error source to users (fix(manifest): Show error source to users cargo#15939)

r? ghost

[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 a4e8d6d has been approved by weihanglo

It is now in the queue for this repository.

[bors]

⌛ Testing commit a4e8d6d with merge ba4b643...

[bors]

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing ba4b643 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 3f1552a (parent) -> ba4b643 (this PR)

Test differences

Show 2 test diffs

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

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard ba4b6437b301b37a0e1f8f19df74d7d9c832d263 --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. aarch64-apple: 6326.1s -> 4921.9s (-22.2%)
2. dist-armhf-linux: 4841.9s -> 5562.8s (14.9%)
3. dist-android: 1464.0s -> 1655.0s (13.0%)
4. dist-aarch64-apple: 8495.3s -> 7403.5s (-12.9%)
5. i686-gnu-2: 5519.9s -> 6184.7s (12.0%)
6. dist-x86_64-apple: 7347.0s -> 8115.1s (10.5%)
7. armhf-gnu: 4741.8s -> 5229.6s (10.3%)
8. x86_64-gnu-llvm-19-2: 5489.9s -> 6044.3s (10.1%)
9. dist-aarch64-msvc: 5972.1s -> 5407.1s (-9.5%)
10. i686-gnu-nopt-1: 7333.5s -> 8023.2s (9.4%)

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 (ba4b643): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

Results (primary -2.4%, secondary -1.5%)

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)	2.3%	[2.2%, 2.4%]	2
Improvements ✅ (primary)	-2.4%	[-2.4%, -2.4%]	1
Improvements ✅ (secondary)	-5.3%	[-8.4%, -2.3%]	2
All ❌✅ (primary)	-2.4%	[-2.4%, -2.4%]	1

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 474.121s -> 472.311s (-0.38%)
Artifact size: 390.61 MiB -> 390.62 MiB (0.00%)