Update cargo submodule

[weihanglo]

7 commits in fe63976b245b8a649c3f2949bf89fdc307bfbae4..598ab48ec328e3e4f5e4e373d8df7264bc8e27cd
2026-06-11 09:17:57 +0000 to 2026-06-17 02:39:50 +0000

• Improved the test error messages when 'rustc -V' fails (Improved the test error messages when 'rustc -V' fails cargo#17108)
• test(install): cargo install --path honors MSRV (test(install): cargo install --path honors MSRV cargo#17102)
• feat(trim-paths): emit CARGO_TRIM_PATHS_REMAP for build.rs (feat(trim-paths): emit CARGO_TRIM_PATHS_REMAP for build.rs cargo#17104)
• Add funding links (Add funding links cargo#17103)
• fix(diag): Give diagnostics the same display path behavior as rustc (fix(diag): Give diagnostics the same display path behavior as rustc cargo#17101)
• refactor: remove cargo-util-terminal from bump-check exclusions (refactor: remove cargo-util-terminal from bump-check exclusions cargo#17098)
• fix(diag): Report all errors, in order (fix(diag): Report all errors, in order cargo#17095)

[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

[rust-bors]

📌 Commit 93fa68b has been approved by weihanglo

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: weihanglo
Duration: 3h 22m 36s
Pushing 693b3e4 to main...

[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 1162ebd (parent) -> 693b3e4 (this PR)

Test differences

Show 3 test diffs

Stage 2

• rust_version::cargo_install_path_honors_msrv_config: [missing] -> pass (J0)

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

Job group index

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

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 693b3e4c6e4e686cb9878c1722ad26858b5f1d2a --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. x86_64-msvc-ext3: 1h 3m -> 1h 49m (+72.1%)
2. dist-x86_64-freebsd: 1h -> 1h 35m (+59.0%)
3. test-various: 2h 16m -> 1h 14m (-45.4%)
4. x86_64-gnu-gcc-core-tests: 14m 43s -> 8m 16s (-43.8%)
5. x86_64-msvc-ext2: 1h 25m -> 2h (+41.0%)
6. x86_64-mingw-2: 2h 6m -> 2h 49m (+34.2%)
7. dist-powerpc-linux: 1h 14m -> 1h 35m (+29.1%)
8. dist-loongarch64-linux: 1h 29m -> 1h 55m (+28.7%)
9. armhf-gnu: 1h 35m -> 1h 9m (-27.7%)
10. pr-check-2: 42m 46s -> 31m 45s (-25.8%)

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

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

This perf run didn't have relevant results for this metric.

Cycles

Results (secondary -3.1%)

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)	-3.1%	[-3.1%, -3.1%]	1
All ❌✅ (primary)	-	-	0

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 521.352s -> 522.375s (0.20%)
Artifact size: 401.86 MiB -> 401.89 MiB (0.01%)