Rollup of 2 pull requests

[JonathanBrouwer]

Successful merges:

• Ensure ErasedData only implements appropriate auto traits #154229 (Ensure ErasedData only implements appropriate auto traits)
• Update try_blocks to a new tracking issue number #154409 (Update try_blocks to a new tracking issue number)

r? @ghost

Create a similar rollup

[JonathanBrouwer]

@bors r+ rollup=never p=5

[rust-bors]

📌 Commit e06b9bb has been approved by JonathanBrouwer

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 11m 30s
Pushing 3a933e5 to main...

[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 3ea2fbc (parent) -> 3a933e5 (this PR)

Test differences

Show 2 test diffs

2 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 3a933e5bf5b695faf9e09d47a263a20c6b85c26a --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-gnu-miri: 1h 19m -> 1h 36m (+21.6%)
2. pr-check-1: 28m 20s -> 33m 31s (+18.3%)
3. dist-aarch64-apple: 1h 31m -> 1h 47m (+17.7%)
4. i686-gnu-2: 1h 29m -> 1h 45m (+17.2%)
5. dist-i586-gnu-i586-i686-musl: 1h 41m -> 1h 25m (-15.8%)
6. dist-x86_64-apple: 1h 44m -> 1h 59m (+14.1%)
7. dist-armhf-linux: 1h 21m -> 1h 33m (+14.0%)
8. optional-x86_64-gnu-parallel-frontend: 2h 22m -> 2h 41m (+13.2%)
9. dist-aarch64-msvc: 1h 37m -> 1h 49m (+12.5%)
10. aarch64-apple: 2h 36m -> 2h 55m (+12.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.

[rust-timer]

Finished benchmarking commit (3a933e5): comparison URL.

Overall result: ✅ improvements - 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
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.0%	[-0.0%, -0.0%]	1
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary -2.1%)

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)	-2.1%	[-2.1%, -2.1%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-2.1%	[-2.1%, -2.1%]	1

Cycles

Results (primary 2.3%, secondary -2.1%)

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

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

Binary size

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

Bootstrap: 485.545s -> 484.487s (-0.22%)
Artifact size: 395.12 MiB -> 395.09 MiB (-0.01%)