Update cargo submodule

[weihanglo]

10 commits in ce69df6f72a3b6a2b5c722ba68ddef255344b31c..8cc0cb136772b8f54eafe0d163fcb7226a06af0c
2026-02-12 12:39:45 +0000 to 2026-02-17 12:16:26 +0000

• docs(layout): Updated layout module docs to document new layout (docs(layout): Updated layout module docs to document new layout cargo#16502)
• fix(host-config): host.linker should not apply to non host unit (fix(host-config): host.linker should not apply to non host unit cargo#16641)
• init: improve error message and add tests (init: improve error message and add tests cargo#16643)
• Corrected doc comment for build script root_output path (Corrected doc comment for build script root_output path cargo#16645)
• Changed build script run output dir to stdout in new build-dir layout (Changed build script run output dir to stdout in new build-dir layout cargo#16644)
• test: add test case for verify-project with invalid TOML (test: add test case for verify-project with invalid TOML cargo#16640)
• test(script): Show remaining workspace behavors (test(script): Show remaining workspace behavors cargo#16633)
• fix(host-config): host.runner should not apply to cargo run (fix(host-config): host.runner should not apply to cargo run cargo#16638)
• refactor(help): simplify code structure (refactor(help): simplify code structure cargo#16627)
• test: Remove unused docker ip_address (test: Remove unused docker ip_address cargo#16636)

[rustbot]

Some changes occurred in src/tools/enzyme

cc @ZuseZ4

Some changes occurred in src/tools/cargo

cc @ehuss

[rustbot]

r? @ehuss

rustbot has assigned @ehuss.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: @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 821ed6c has been approved by weihanglo

It is now in the queue for this repository.

[weihanglo]

@bors r+ rollup=never p=1

[rust-bors]

📌 Commit 821ed6c has been approved by weihanglo

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: weihanglo
Duration: 3h 26m 28s
Pushing 99246f4 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 3fc3732 (parent) -> 99246f4 (this PR)

Test differences

Show 13 test diffs

Stage 2

• build_script::host_runner_does_not_apply_to_cargo_run: [missing] -> pass (J0)
• cargo_init::error_on_existing_package::init_error_on_existing_package: [missing] -> pass (J0)
• cargo_init::reserved_name_core::init_with_reserved_name_core: [missing] -> pass (J0)
• cross_compile::host_linker_does_not_apply_to_binary_build: [missing] -> pass (J0)
• script::cargo::package_workspace: [missing] -> ignore (-Zscript is unstable) (J0)
• script::cargo::workspace_members_glob_matches_script: [missing] -> ignore (-Zscript is unstable) (J0)
• script::cargo::workspace_members_mentions_script: [missing] -> ignore (-Zscript is unstable) (J0)
• tool_paths::custom_runner_target_applies_to_host: [missing] -> pass (J0)
• verify_project::verify_project_invalid_toml_syntax: [missing] -> pass (J0)

Additionally, 4 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 99246f40931ce1d1d29517b61bd70dd9ed4fbe5d --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-gnu-debug: 2h 7m -> 1h 44m (-17.7%)
2. x86_64-gnu-miri: 1h 22m -> 1h 8m (-16.5%)
3. arm-android: 1h 46m -> 1h 30m (-15.1%)
4. i686-gnu-2: 1h 47m -> 1h 32m (-14.2%)
5. x86_64-rust-for-linux: 53m 22s -> 45m 57s (-13.9%)
6. dist-x86_64-apple: 2h 8m -> 1h 51m (-13.3%)
7. i686-gnu-1: 2h 29m -> 2h 10m (-13.3%)
8. x86_64-gnu-tools: 1h 4m -> 56m 22s (-12.7%)
9. test-various: 2h 5m -> 1h 49m (-12.7%)
10. aarch64-msvc-2: 1h 52m -> 1h 39m (-12.2%)

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 (99246f4): 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)

Results (secondary -3.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)	-	-	0
Improvements ✅ (secondary)	-3.9%	[-3.9%, -3.9%]	1
All ❌✅ (primary)	-	-	0

Cycles

Results (secondary 3.2%)

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

Binary size

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

Bootstrap: 482.367s -> 482.582s (0.04%)
Artifact size: 397.92 MiB -> 397.92 MiB (0.00%)