Update cargo submodule

[weihanglo]

9 commits in 94c368ad2b9db0f0da5bdd8421cea13786ce4412..b54051b1505281ec7a45a250140a0ff25d33f319
2025-12-26 19:39:15 +0000 to 2025-12-30 20:35:52 +0000

• fix(log): add dependencies field to UnitRegistered (fix(log): add dependencies field to UnitRegistered cargo#16448)
• Implement fine grain locking for build-dir (Implement fine grain locking for build-dir cargo#16155)
• feat(resolver): List features when no close match (feat(resolver): List features when no close match cargo#16445)
• feat(report): new command cargo report sessions (feat(report): new command cargo report sessions cargo#16428)
• feat (patch): Display where the patch was defined in patch-related error messages (feat (patch): Display where the patch was defined in patch-related error messages cargo#16407)
• test(build-rs): Reduce from 'build' to 'check' where possible (test(build-rs): Reduce from 'build' to 'check' where possible cargo#16444)
• feat(toml): TOML 1.1 parse support (feat(toml): TOML 1.1 parse support cargo#16415)
• feat(report): support --manifest-path in cargo report timings (feat(report): support --manifest-path in cargo report timings cargo#16441)
• fix(vendor): recursively filter git files in subdirectories (fix(vendor): recursively filter git files in subdirectories cargo#16439)

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 62d1910 has been approved by weihanglo

It is now in the queue for this repository.

[bors]

⌛ Testing commit 62d1910 with merge 629b092...

[bors]

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

Test differences

Show 20 test diffs

Stage 2

• cargo_report_sessions::existing_logs_from_other_workspaces: [missing] -> pass (J0)
• cargo_report_sessions::gated_stable_channel: [missing] -> pass (J0)
• cargo_report_sessions::gated_unstable_options: [missing] -> pass (J0)
• cargo_report_sessions::help::case: [missing] -> pass (J0)
• cargo_report_sessions::in_workspace: [missing] -> pass (J0)
• cargo_report_sessions::no_logs: [missing] -> pass (J0)
• cargo_report_sessions::no_logs_in_workspace: [missing] -> pass (J0)
• cargo_report_sessions::outside_workspace: [missing] -> pass (J0)
• cargo_report_sessions::with_limit_1_and_extra_logs: [missing] -> pass (J0)
• cargo_report_sessions::with_limit_5_but_not_enough_logs: [missing] -> pass (J0)
• cargo_report_sessions::with_manifest_path: [missing] -> pass (J0)
• cargo_report_timings::with_manifest_path: [missing] -> pass (J0)
• features::dependency_activates_feature_with_no_close_match: [missing] -> pass (J0)
• patch::mismatched_version_from_cli_config: [missing] -> pass (J0)
• patch::mismatched_version_from_config_file_provided_via_cli: [missing] -> pass (J0)
• patch::patch_from_env_config_is_ignored: [missing] -> pass (J0)
• patch::patch_same_version_different_patch_locations: [missing] -> pass (J0)
• vendor::vendor_filters_git_files_recursively: [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 629b092f8fab1b0370dfb749c4f5e00e70169dd2 --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-gcc: 3689.4s -> 3060.6s (-17.0%)
2. pr-check-1: 1991.1s -> 1677.0s (-15.8%)
3. aarch64-apple: 12398.9s -> 10542.6s (-15.0%)
4. test-various: 7734.7s -> 6654.9s (-14.0%)
5. pr-check-2: 2566.2s -> 2216.8s (-13.6%)
6. x86_64-gnu-tools: 3691.0s -> 3241.3s (-12.2%)
7. i686-gnu-2: 6055.6s -> 5319.3s (-12.2%)
8. i686-gnu-nopt-1: 8407.9s -> 7387.9s (-12.1%)
9. aarch64-gnu-llvm-20-2: 3040.9s -> 2681.7s (-11.8%)
10. aarch64-gnu-debug: 4350.7s -> 3851.6s (-11.5%)

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 (629b092): 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

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

Binary size

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

Bootstrap: 481.911s -> 479.804s (-0.44%)
Artifact size: 390.84 MiB -> 390.89 MiB (0.01%)