Weekly cargo update

[github-actions]

Automation to keep dependencies in Cargo.lock current.
r? dep-bumps

The following is the output from cargo update:

compiler & tools dependencies:
     Locking 6 packages to latest compatible versions
      Adding io-uring v0.7.8
    Updating jsonpath-rust v1.0.2 -> v1.0.3
    Updating libffi v4.1.0 -> v4.1.1
    Updating libffi-sys v3.3.1 -> v3.3.2
    Updating tokio v1.45.1 -> v1.46.1
    Updating wasm-component-ld v0.5.14 -> v0.5.15
note: pass `--verbose` to see 41 unchanged dependencies behind latest

library dependencies:
     Locking 0 packages to latest compatible versions
note: pass `--verbose` to see 4 unchanged dependencies behind latest

rustbook dependencies:
     Locking 1 package to latest compatible version
    Updating cc v1.2.27 -> v1.2.29

[rustbot]

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

[clubby789]

@bors r+ rollup=never

[bors]

📌 Commit 31ea5f9 has been approved by clubby789

It is now in the queue for this repository.

[bors]

⌛ Testing commit 31ea5f9 with merge 3c95364...

[bors]

☀️ Test successful - checks-actions
Approved by: clubby789
Pushing 3c95364 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 c83e217 (parent) -> 3c95364 (this PR)

Test differences

Show 2 test diffs

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

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 3c95364c4afc3f15749f5a511d599af086f5456e --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-apple-2: 5079.7s -> 3319.4s (-34.7%)
2. x86_64-apple-1: 8269.4s -> 5964.0s (-27.9%)
3. dist-apple-various: 6124.8s -> 7270.1s (18.7%)
4. x86_64-rust-for-linux: 2947.9s -> 2528.3s (-14.2%)
5. x86_64-gnu-llvm-19-1: 3801.8s -> 3409.7s (-10.3%)
6. tidy: 77.9s -> 70.1s (-10.0%)
7. x86_64-gnu-tools: 3648.5s -> 3310.3s (-9.3%)
8. aarch64-apple: 4398.2s -> 4001.9s (-9.0%)
9. pr-check-2: 2035.0s -> 1860.3s (-8.6%)
10. i686-gnu-1: 7910.8s -> 7236.6s (-8.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 (3c95364): comparison URL.

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

Max RSS (memory usage)

Results (secondary -4.5%)

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

Cycles

Results (primary -1.7%, secondary 2.7%)

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.7%	[3.0%, 4.6%]	6
Improvements ✅ (primary)	-1.7%	[-1.7%, -1.7%]	1
Improvements ✅ (secondary)	-3.7%	[-3.7%, -3.7%]	1
All ❌✅ (primary)	-1.7%	[-1.7%, -1.7%]	1

Binary size

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

Bootstrap: 461.809s -> 461.042s (-0.17%)
Artifact size: 372.19 MiB -> 372.12 MiB (-0.02%)