Rollup of 4 pull requests

[JonathanBrouwer]

Successful merges:

• Use &C::Key less in queries. #153464 (Use &C::Key less in queries.)
• Remove the rustc_data_structures::assert_matches! re-exports #153553 (Remove the rustc_data_structures::assert_matches! re-exports)
• Replace the try_mark_green hook with direct calls to tcx.dep_graph #153561 (Replace the try_mark_green hook with direct calls to tcx.dep_graph)
• rendering interpreter OOM as OOM instead of ICE #153564 (rendering interpreter OOM as OOM instead of ICE)

r? @ghost

Create a similar rollup

[JonathanBrouwer]

@bors r+ rollup=never p=5

[rust-bors]

📌 Commit f0defb0 has been approved by JonathanBrouwer

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 26m 35s
Pushing b41f22d to main...

[rust-timer]

📌 Perf builds for each rolled up PR:

PR#	Message	Perf Build Sha
#153464	Use &C::Key less in queries.	a181aca71f35ecefa2c5d64269cd96ba83831ab0 (link)
#153553	Remove the rustc_data_structures::assert_matches! re-expo…	82a2b895211a6f661f1d9f07054d3bd2a450be00 (link)
#153561	Replace the try_mark_green hook with direct calls to `tcx…	ec1f716981da8f272b6ac7d9d629adb6ad02e70d (link)
#153564	rendering interpreter OOM as OOM instead of ICE	a9b334783aeb94060f373dbfd4064ed6f5e7ab55 (link)

previous master: c7b206bba4

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

[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 c7b206b (parent) -> b41f22d (this PR)

Test differences

Show 122 test diffs

122 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 b41f22de2a13a0babd28771e96feef4c309f54aa --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-aarch64-linux: 2h 54m -> 1h 51m (-36.0%)
2. dist-aarch64-llvm-mingw: 1h 37m -> 1h 50m (+13.5%)
3. dist-apple-various: 2h 3m -> 1h 48m (-12.3%)
4. i686-gnu-nopt-2: 2h 12m -> 2h 26m (+11.0%)
5. dist-aarch64-msvc: 1h 50m -> 1h 39m (-9.8%)
6. x86_64-msvc-2: 2h 17m -> 2h 28m (+8.2%)
7. x86_64-gnu-miri: 1h 27m -> 1h 34m (+8.0%)
8. dist-x86_64-freebsd: 1h 22m -> 1h 28m (+7.8%)
9. x86_64-gnu-llvm-20-2: 1h 38m -> 1h 45m (+7.2%)
10. dist-arm-linux-musl: 1h 31m -> 1h 37m (+6.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 (b41f22d): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

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

Max RSS (memory usage)

Results (primary -0.3%, secondary 1.0%)

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

	mean	range	count
Regressions ❌ (primary)	1.4%	[1.4%, 1.4%]	1
Regressions ❌ (secondary)	5.8%	[5.8%, 5.8%]	1
Improvements ✅ (primary)	-2.1%	[-2.1%, -2.1%]	1
Improvements ✅ (secondary)	-3.8%	[-3.8%, -3.8%]	1
All ❌✅ (primary)	-0.3%	[-2.1%, 1.4%]	2

Cycles

Results (primary -3.2%, secondary -2.4%)

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)	1.5%	[1.5%, 1.5%]	1
Improvements ✅ (primary)	-3.2%	[-3.2%, -3.2%]	1
Improvements ✅ (secondary)	-4.4%	[-4.8%, -4.0%]	2
All ❌✅ (primary)	-3.2%	[-3.2%, -3.2%]	1

Binary size

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

Bootstrap: 488.157s -> 478.517s (-1.97%)
Artifact size: 395.01 MiB -> 395.02 MiB (0.00%)