Weekly cargo update

[github-actions]

Automation to keep dependencies in Cargo.lock current.

The following is the output from cargo update:

compiler & tools dependencies:
     Locking 23 packages to latest compatible versions
    Updating anstyle-svg v0.1.8 -> v0.1.9
    Updating autocfg v1.4.0 -> v1.5.0
    Updating bumpalo v3.18.1 -> v3.19.0
    Updating derive-where v1.4.0 -> v1.5.0
    Updating errno v0.3.12 -> v0.3.13
    Updating indexmap v2.9.0 -> v2.10.0
    Updating libredox v0.1.3 -> v0.1.4
    Updating owo-colors v4.2.1 -> v4.2.2
    Updating pest v2.8.0 -> v2.8.1
    Updating pest_derive v2.8.0 -> v2.8.1
    Updating pest_generator v2.8.0 -> v2.8.1
    Updating pest_meta v2.8.0 -> v2.8.1
    Updating r-efi v5.2.0 -> v5.3.0
    Updating rustc-build-sysroot v0.5.8 -> v0.5.9
    Updating slab v0.4.9 -> v0.4.10
    Updating syn v2.0.103 -> v2.0.104
      Adding toml v0.8.23
      Adding toml_edit v0.22.27
      Adding toml_write v0.1.2
    Updating tracing-attributes v0.1.29 -> v0.1.30
    Updating xattr v1.5.0 -> v1.5.1
    Updating zerocopy v0.8.25 -> v0.8.26
    Updating zerocopy-derive v0.8.25 -> v0.8.26
note: pass `--verbose` to see 39 unchanged dependencies behind latest

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

rustbook dependencies:
     Locking 21 packages to latest compatible versions
    Updating autocfg v1.4.0 -> v1.5.0
    Updating bumpalo v3.18.1 -> v3.19.0
    Updating errno v0.3.12 -> v0.3.13
    Updating indexmap v2.9.0 -> v2.10.0
    Updating markup5ever v0.16.1 -> v0.16.2
    Updating pest v2.8.0 -> v2.8.1
    Updating pest_derive v2.8.0 -> v2.8.1
    Updating pest_generator v2.8.0 -> v2.8.1
    Updating pest_meta v2.8.0 -> v2.8.1
    Updating r-efi v5.2.0 -> v5.3.0
    Updating syn v2.0.103 -> v2.0.104
      Adding windows-sys v0.60.2
      Adding windows-targets v0.53.2
      Adding windows_aarch64_gnullvm v0.53.0
      Adding windows_aarch64_msvc v0.53.0
      Adding windows_i686_gnu v0.53.0
      Adding windows_i686_gnullvm v0.53.0
      Adding windows_i686_msvc v0.53.0
      Adding windows_x86_64_gnu v0.53.0
      Adding windows_x86_64_gnullvm v0.53.0
      Adding windows_x86_64_msvc v0.53.0

[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

[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.

[ehuss]

r? clubby789

[clubby789]

@bors r+ rollup=never

[bors]

📌 Commit 6de70b7 has been approved by clubby789

It is now in the queue for this repository.

[workingjubilee]

forcing rollup=never drain:

@bors p=5

[bors]

⌛ Testing commit 6de70b7 with merge 08e3750...

[bors]

💔 Test failed - checks-actions

[clubby789]

tidy error: once_cell is registered in src/bootstrap/src/utils/proc_macro_deps.rs, but is not a proc-macro crate dependency

[clubby789]

@bors r+ rollup=never

[bors]

📌 Commit 8392871 has been approved by clubby789

It is now in the queue for this repository.

[clubby789]

@bors r+ rollup=never p=0

(no longer needs to be drained urgently)

[bors]

📌 Commit 5737b85 has been approved by clubby789

It is now in the queue for this repository.

[bors]

⌛ Testing commit 5737b85 with merge 48aee7e...

[bors]

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

Test differences

Show 1 test diff

1 doctest diff were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 48aee7e383503c234cce4206dee9f19f57edb617 --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: 5069.4s -> 3986.1s (-21.4%)
2. x86_64-apple-1: 9091.3s -> 7670.7s (-15.6%)
3. aarch64-apple: 5667.5s -> 4858.5s (-14.3%)
4. tidy: 75.9s -> 85.6s (12.8%)
5. x86_64-gnu-nopt: 7365.3s -> 8222.0s (11.6%)
6. i686-msvc-2: 7986.8s -> 7213.9s (-9.7%)
7. dist-armhf-linux: 4643.3s -> 4995.6s (7.6%)
8. dist-x86_64-solaris: 5385.5s -> 5003.5s (-7.1%)
9. dist-apple-various: 6792.2s -> 7215.7s (6.2%)
10. aarch64-gnu: 6630.6s -> 7007.4s (5.7%)

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.