Update cargo submodule

[weihanglo]

13 commits in 761c4658d0079d607e6d33cf0c060e61a617cad3..24bb93c388fb8c211a37986539f24a819dc669d3
2025-09-04 01:25:01 +0000 to 2025-09-10 23:16:07 +0000

• Bump miow to 0.60.1 (Bump miow to 0.60.1 cargo#15950)
• test(help): Ensure consistent behavior regardless of rustup use (test(help): Ensure consistent behavior regardless of rustup use cargo#15949)
• docs(changelog): Clarify how manifest paths are used (docs(changelog): Clarify how manifest paths are used cargo#15946)
• fix(flock): check if they are marked unsupported in libstd (fix(flock): check if they are marked unsupported in libstd cargo#15941)
• test(manifest): Fix test output order (test(manifest): Fix test output order cargo#15940)
• refactor(shell): Simplify some code (refactor(shell): Simplify some code cargo#15937)
• fix(manifest): Report script manifest errors for the right line number (fix(manifest): Report script manifest errors for the right line number cargo#15927)
• refactor: replace flock with std flock (refactor: replace flock with std flock cargo#15935)
• fix(cli): Adjust messages to match rustc (fix(cli): Adjust messages to match rustc  cargo#15928)
• fix: Switch from --nocapture to --no-capture (fix: Switch from --nocapture to --no-capture cargo#15930)
• Render individual compilation sections in --timings pipeline graph (Render individual compilation sections in --timings pipeline graph cargo#15923)
• test(credential): Switch more expected results to snapshots (test(credential): Switch more expected results to snapshots cargo#15929)
• refactor(cli): Pull out error chain iteration (refactor(cli): Pull out error chain iteration cargo#15926)

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

It is now in the queue for this repository.

[bors]

⌛ Testing commit a014994 with merge a312b65...

[bors]

💔 Test failed - checks-actions

[weihanglo]

@bors r+ rollup=never p=1

[bors]

📌 Commit c3bd8b6 has been approved by weihanglo

It is now in the queue for this repository.

[bors]

⌛ Testing commit c3bd8b6 with merge 5eda692...

[bors]

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing 5eda692 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 76c5ed2 (parent) -> 5eda692 (this PR)

Test differences

Show 4 test diffs

Stage 2

• script::cargo::manifest_parse_error: [missing] -> ignore (-Zscript is unstable) (J0)

Additionally, 3 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 5eda692e73f37dcbe2437ce878db7bb71f323e74 --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-powerpc64-linux: 5512.8s -> 5079.4s (-7.9%)
2. aarch64-msvc-1: 7364.3s -> 6810.3s (-7.5%)
3. dist-ohos-aarch64: 4434.6s -> 4155.3s (-6.3%)
4. dist-various-1: 3913.8s -> 4143.4s (5.9%)
5. dist-apple-various: 4455.8s -> 4687.7s (5.2%)
6. dist-i686-msvc: 8039.7s -> 7655.5s (-4.8%)
7. dist-i686-linux: 6308.3s -> 6007.0s (-4.8%)
8. dist-armhf-linux: 4954.0s -> 5190.3s (4.8%)
9. dist-various-2: 2200.9s -> 2097.4s (-4.7%)
10. aarch64-gnu-llvm-19-2: 2229.2s -> 2125.6s (-4.6%)

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 (5eda692): 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 -2.6%)

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

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: 466.951s -> 467.659s (0.15%)
Artifact size: 387.77 MiB -> 387.85 MiB (0.02%)