Update cargo

[ehuss]

9 commits in 145219a9f089f8b57c09f40525374fbade1e34ae..0e474cfd7b16b018cf46e95da3f6a5b2f1f6a9e7
2023-03-27 01:56:36 +0000 to 2023-03-31 23:15:58 +0000

• Add delays to network retries. (Add delays to network retries. cargo#11881)
• Add a note to cargo logout that it does not revoke the token. (Add a note to cargo logout that it does not revoke the token. cargo#11919)
• Sync external-tools JSON docs. (Sync external-tools JSON docs. cargo#11918)
• Drop derive feature from serde in cargo-platform (Drop derive feature from serde in cargo-platform cargo#11915)
• Disable test_profile test on windows-gnu (Disable test_profile test on windows-gnu cargo#11916)
• src/doc/src/reference/build-scripts.md: a{n =>} benchmark target (src/doc/src/reference/build-scripts.md: a{n =>} benchmark target cargo#11908)
• Documented working directory behaviour for cargo test, cargo bench and cargo run (Documented working directory behaviour for cargo test, cargo bench and cargo run cargo#11901)
• docs(contrib): Link to office hours doc (docs(contrib): Link to office hours doc cargo#11903)
• chore: Upgrade to clap v4.2 (chore: Upgrade to clap v4.2 cargo#11904)

[rustbot]

⚠️ Warning ⚠️

• These commits modify submodules.

[rustbot]

These commits modify the Cargo.lock file. Random changes to Cargo.lock can be introduced when switching branches and rebasing PRs.
This was probably unintentional and should be reverted before this PR is merged.

If this was intentional then you can ignore this comment.

[ehuss]

@bors r+ p=1

[bors]

📌 Commit 6e29862 has been approved by ehuss

It is now in the queue for this repository.

[bors]

⌛ Testing commit 6e29862 with merge 0196c2b...

[bors]

☀️ Test successful - checks-actions
Approved by: ehuss
Pushing 0196c2b to master...

[rust-timer]

Finished benchmarking commit (0196c2b): comparison URL.

Overall result: ❌ regressions - 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.6%	[0.6%, 0.6%]	3
Regressions ❌ (secondary)	0.4%	[0.2%, 0.6%]	9
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.6%	[0.6%, 0.6%]	3

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

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

Cycles

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

[lqd]

I believe all these benchmarks to be currently noisy, unfortunately.