Update cargo submodule

[weihanglo]

8 commits in 0c9e687d237ff04b53ccb67b4ce63e9483789e88..ce69df6f72a3b6a2b5c722ba68ddef255344b31c
2026-02-11 05:58:30 +0000 to 2026-02-12 12:39:45 +0000

• fix: apply host.runner only when host-config enabled (fix: apply host.runner only when host-config enabled cargo#16631)
• fix(cli): Improve bad manifest error ( fix(cli): Improve bad manifest error  cargo#16630)
• fix: Adjust casing of error message (fix: Adjust casing of error message cargo#16625)
• Enable triagebot new [view-all-comments-link] feature (Enable triagebot new [view-all-comments-link] feature cargo#16629)
• test(help): snapshot cargo help tests (test(help): snapshot cargo help tests cargo#16626)
• Suggest a workspace.members entry even from outside the workspace root (Suggest a workspace.members entry even from outside the workspace root cargo#16616)
• Reorganize build unit directory layout for new build-dir layout (Reorganize build unit directory layout for new build-dir layout cargo#16542)
• Make the error messaging for cargo install aware of build.build-dir (Make the error messaging for cargo install aware of build.build-dir cargo#16623)

[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-lang/cargo#16631 fixes a relatively severe regression. See #miri > build-script-build contains outdated or invalid JSON

[rust-bors]

📌 Commit a0eb38a has been approved by weihanglo

It is now in the queue for this repository.

[RalfJung]

@bors p=10
due to the regression fix

[rust-bors]

☀️ Test successful - CI
Approved by: weihanglo
Duration: 4h 19m 25s
Pushing 47611e1 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 bb8b30a (parent) -> 47611e1 (this PR)

Test differences

Show 17 test diffs

Stage 2

• build_script::target_runner_does_not_apply_to_build_script: [missing] -> pass (J0)
• cargo_help::nested_alias_dash_joined::case: [missing] -> pass (J0)
• cargo_help::nested_cmd::case: [missing] -> pass (J0)
• cargo_help::nested_cmd_dash_joined::case: [missing] -> pass (J0)
• cargo_help::nested_cmd_suggestion::case: [missing] -> pass (J0)
• cargo_help::nested_cmd_with_extra_flags::case: [missing] -> pass (J0)
• cargo_help::nested_subcommand_suggestion::case: [missing] -> pass (J0)
• cargo_help::single_alias::case: [missing] -> pass (J0)
• cargo_help::single_cmd::case: [missing] -> pass (J0)
• cargo_help::single_cmd_space_joined::case: [missing] -> pass (J0)
• cargo_help::single_cmd_suggestion::case: [missing] -> pass (J0)
• cargo_help::single_cmd_with_extra_flags::case: [missing] -> pass (J0)
• install::failed_install_points_to_build_dir_for_intermediate_artifacts: [missing] -> pass (J0)
• workspaces::error_if_manifest_path_is_relative: [missing] -> pass (J0)
• workspaces::error_if_member_is_outside_root: [missing] -> pass (J0)

Additionally, 2 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 47611e16044c68ef27bac31c35fda2ba1dc20b73 --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: 2h 19m -> 1h 49m (-21.5%)
2. dist-aarch64-msvc: 1h 34m -> 1h 53m (+21.0%)
3. test-various: 2h 9m -> 1h 43m (-20.5%)
4. dist-aarch64-apple: 2h 57m -> 2h 21m (-20.2%)
5. x86_64-gnu-nopt: 2h 6m -> 2h 22m (+13.3%)
6. x86_64-gnu-llvm-21-3: 1h 38m -> 1h 51m (+13.2%)
7. x86_64-rust-for-linux: 47m 24s -> 42m 39s (-10.0%)
8. tidy: 2m 43s -> 2m 55s (+7.8%)
9. aarch64-gnu-debug: 1h 14m -> 1h 8m (-7.5%)
10. dist-arm-linux-gnueabi: 1h 24m -> 1h 29m (+6.9%)

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

Overall result: ❌✅ regressions and improvements - no action needed

@rustbot label: -perf-regression

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)	-	-	0
Regressions ❌ (secondary)	0.6%	[0.1%, 1.1%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.1%	[-0.2%, -0.0%]	2
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary -2.8%)

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.8%	[-2.8%, -2.7%]	2
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-2.8%	[-2.8%, -2.7%]	2

Cycles

Results (primary -2.1%, secondary 1.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)	4.0%	[2.5%, 6.6%]	6
Improvements ✅ (primary)	-2.1%	[-2.1%, -2.1%]	1
Improvements ✅ (secondary)	-5.2%	[-7.1%, -3.8%]	3
All ❌✅ (primary)	-2.1%	[-2.1%, -2.1%]	1

Binary size

Results (primary 0.1%, secondary 0.1%)

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

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

Bootstrap: 480.389s -> 482.691s (0.48%)
Artifact size: 396.04 MiB -> 398.13 MiB (0.53%)