Update cargo

[weihanglo]

8 commits in 6833aa715d724437dc1247d0166afe314ab6854e..9b296973b425ffb159e12cf3cd56580fd5c85382
2025-07-13 02:25:52 +0000 to 2025-07-25 17:10:08 +0000

• Allow using Cargo-as-a-library with gix's reqwest backend (Allow using Cargo-as-a-library with gix's reqwest backend cargo#15653)
• Make timings graphs scalable to user's window (Make timings graphs scalable to user's window cargo#15766)
• refactor: rename arg mode to intent (refactor: rename arg mode to intent cargo#15774)
• fix: no-proc-macro is overridden by subsequent edges (fix: no-proc-macro is overridden by subsequent edges cargo#15764)
• Use gix for cargo package (Use gix for cargo package cargo#15534)
• cargo-credential-libsecret: give FFI correctly-sized object (cargo-credential-libsecret: give FFI correctly-sized object cargo#15767)
• Remove unnecessary target-c-int-width from target specs (Remove unnecessary target-c-int-width from target specs cargo#15759)
• Expose artifact dependency getters in cargo-as-a-library (Expose artifact dependency getters in cargo-as-a-library cargo#15753)

[rustbot]

Some changes occurred in src/tools/cargo

cc @ehuss

[rustbot]

⚠️ Warning ⚠️

• Some commits in this PR modify submodules.

[weihanglo]

Hmm… much less commits than I thought, probably do it later on Friday.

[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

[weihanglo]

@bors r+ rollup=never p=1

[bors]

📌 Commit 98af662 has been approved by weihanglo

It is now in the queue for this repository.

[bors]

⌛ Testing commit 98af662 with merge 0d8ea0f...

[ehuss]

@bors r-

Looks like a license error.

[bors]

💔 Test failed - checks-actions

[rustbot]

There are changes to the tidy tool.

cc @jieyouxu

The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging.

cc @davidtwco, @wesleywiser

[weihanglo]

@bors r+ rollup=never p=1

[bors]

📌 Commit a1e292a has been approved by weihanglo

It is now in the queue for this repository.

[bors]

⌛ Testing commit a1e292a with merge 0dd07bd...

[bors]

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing 0dd07bd 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 430d6ed (parent) -> 0dd07bd (this PR)

Test differences

Show 3 test diffs

Stage 2

• cargo_tree::deps::no_proc_macro_order: [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 0dd07bd2165db70ffbe0b903635de26ca630bf20 --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-apple-various: 8300.5s -> 6131.1s (-26.1%)
2. x86_64-apple-1: 9248.4s -> 7242.5s (-21.7%)
3. dist-aarch64-apple: 6183.0s -> 7465.3s (20.7%)
4. x86_64-apple-2: 5742.1s -> 4647.7s (-19.1%)
5. x86_64-gnu-tools: 3303.0s -> 3892.1s (17.8%)
6. x86_64-msvc-1: 9205.7s -> 8344.3s (-9.4%)
7. aarch64-msvc-2: 5785.0s -> 5271.3s (-8.9%)
8. x86_64-msvc-ext2: 5531.6s -> 5908.4s (6.8%)
9. dist-x86_64-freebsd: 4932.0s -> 5227.6s (6.0%)
10. x86_64-gnu-llvm-19: 2503.3s -> 2649.0s (5.8%)

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 (0dd07bd): comparison URL.

Overall result: ❌ regressions - 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.4%	[0.3%, 0.6%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary 2.9%, secondary 0.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	2.9%	[2.9%, 2.9%]	1
Regressions ❌ (secondary)	2.0%	[1.8%, 2.3%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-3.3%	[-3.3%, -3.3%]	1
All ❌✅ (primary)	2.9%	[2.9%, 2.9%]	1

Cycles

Results (secondary -2.3%)

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.3%	[-2.3%, -2.2%]	2
All ❌✅ (primary)	-	-	0

Binary size

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

Bootstrap: 468.925s -> 467.876s (-0.22%)
Artifact size: 374.68 MiB -> 376.61 MiB (0.52%)