Update cargo

[ehuss]

7 commits in 2251525ae503fa196f6d7f9ce6d32eccb2d5f044..84709f085062cbf3c51fa507527c1b2334015178
2025-06-16 22:01:27 +0000 to 2025-06-22 23:58:39 +0000

• Bump cargo-util-schemas version (Bump cargo-util-schemas version cargo#15696)
• test(msrv): use a far future "newer" version (test(msrv): use a far future "newer" version cargo#15693)
• Plumb rustc -Zhint-mostly-unused flag through as a profile option (Plumb rustc -Zhint-mostly-unused flag through as a profile option cargo#15643)
• Disable lldb test, which seems to be broken due to issues with lldb (Disable lldb test, which seems to be broken due to issues with lldb cargo#15687)
• docs(contrib): change clap URL to docs.rs/clap (docs(contrib): change clap URL to docs.rs/clap cargo#15682)
• feat: Introduce perma unstable --compile-time-deps option for cargo build (feat: Introduce perma unstable --compile-time-deps option for cargo build cargo#15674)
• fix: Failing tests on rustc nightly (fix: Failing tests on rustc nightly cargo#15679)

[rustbot]

⚠️ Warning ⚠️

• Some commits in this PR modify submodules.

[ehuss]

@bors r+ p=1

[bors]

📌 Commit 74973d7 has been approved by ehuss

It is now in the queue for this repository.

[tgross35]

Placing this with the rollups since it's needed for the branch
@bors p=5

[bors]

⌛ Testing commit 74973d7 with merge 58d5e11...

[bors]

☀️ Test successful - checks-actions
Approved by: ehuss
Pushing 58d5e11 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 8387d61 (parent) -> 58d5e11 (this PR)

Test differences

Show 10 test diffs

Stage 2

• compile_time_deps::build_dep: [missing] -> pass (J0)
• compile_time_deps::gated_by_unstable_opts: [missing] -> pass (J0)
• compile_time_deps::indirect_comp_time_dep: [missing] -> pass (J0)
• compile_time_deps::non_comp_time_dep: [missing] -> pass (J0)
• compile_time_deps::proc_macro_dep: [missing] -> pass (J0)
• compile_time_deps::tests_target: [missing] -> pass (J0)
• profiles::profile_hint_mostly_unused_nightly: [missing] -> ignore (-Zhint-mostly-unused is unstable) (J0)
• profiles::profile_hint_mostly_unused_warn_without_gate: [missing] -> pass (J0)
• profile_trim_paths::lldb_works_after_trimmed: ignore (-Zremap-path-scope is unstable) -> [missing] (J1)
• profile_trim_paths::cdb_works_after_trimmed: ignore (-Zremap-path-scope is unstable) -> [missing] (J2)

Job group index

• J0: aarch64-apple, aarch64-gnu, x86_64-gnu-aux, x86_64-msvc-ext1
• J1: aarch64-apple, aarch64-gnu, x86_64-gnu-aux
• J2: x86_64-msvc-ext1

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 58d5e1169056f31553ecf680b009a5770eb0e859 --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: 3312.0s -> 4405.1s (33.0%)
2. aarch64-gnu-debug: 3472.3s -> 4080.9s (17.5%)
3. x86_64-rust-for-linux: 2506.4s -> 2910.8s (16.1%)
4. x86_64-gnu-llvm-20-1: 3212.0s -> 3651.5s (13.7%)
5. dist-aarch64-windows-gnullvm: 4427.4s -> 5018.5s (13.3%)
6. x86_64-gnu-llvm-20-3: 6118.7s -> 6875.0s (12.4%)
7. i686-gnu-2: 5435.9s -> 6092.5s (12.1%)
8. arm-android: 5164.8s -> 5779.2s (11.9%)
9. dist-aarch64-apple: 5757.9s -> 6376.5s (10.7%)
10. mingw-check-1: 1581.4s -> 1747.3s (10.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.