Update cargo

[weihanglo]

9 commits in a4c63fe5388beaa09e5f91196c86addab0a03580..7065f0ef4aa267a7455e1c478b5ccacb7baea59c
2024-03-06 22:15:17 +0000 to 2024-03-12 13:25:15 +0000

• chore: remove repetitive word (chore: remove repetitive word cargo#13575)
• refactor(lockfile): Make diffing/printing more reusable (refactor(lockfile): Make diffing/printing more reusable cargo#13564)
• test: Add tests for using worktrees and sparse checkouts (test: Add tests for using worktrees and sparse checkouts cargo#13567)
• util/network/http: Use cargo/1.2.3 user-agent header (util/network/http: Use cargo/1.2.3 user-agent header cargo#13548)
• fix: Consistently compare MSRVs (fix: Consistently compare MSRVs  cargo#13537)
• refactor(shell): Use alternate to close links (refactor(shell): Use alternate to close links cargo#13562)
• fix(doc): Collapse down Generated statuses without --verbose (fix(doc): Collapse down Generated statuses without --verbose  cargo#13557)
• doc: Add doc for -Zpublic-dependency (doc: Add doc for -Zpublic-dependency cargo#13556)
• docs: add link to the exported_private_dependencies lint (docs: add link to the exported_private_dependencies lint cargo#13547)

r? ghost

[rustbot]

Some changes occurred in src/tools/cargo

cc @ehuss

[weihanglo]

@bors r+ rollup=never p=1

[bors]

📌 Commit e322fef has been approved by weihanglo

It is now in the queue for this repository.

[bors]

⌛ Testing commit e322fef with merge a165f1f...

[bors]

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing a165f1f to master...

[bors]

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing a165f1f to master...

[rust-timer]

Finished benchmarking commit (a165f1f): comparison URL.

Overall result: ❌✅ regressions and improvements - ACTION NEEDED

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	1.1%	[1.1%, 1.1%]	1
Improvements ✅ (primary)	-0.7%	[-0.7%, -0.7%]	3
Improvements ✅ (secondary)	-0.5%	[-0.6%, -0.3%]	5
All ❌✅ (primary)	-0.7%	[-0.7%, -0.7%]	3

Max RSS (memory usage)

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

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: 675.268s -> 672.147s (-0.46%)
Artifact size: 310.30 MiB -> 310.26 MiB (-0.01%)

[weihanglo]

Hmm… didn't get it. There is no change obviously affecting performance in Cargo. tt-muncher looks even less relevant.

[Kobzol]

I wouldn't worry about it. Updating cargo almost always introduces small perf. changes, unless something really large stands out, we usually don't deal with it.

[Kobzol]

The muncher change looks like noise, based on the historical chart.

@rustbot label: +perf-regression-triaged