Rollup of 3 pull requests

[jhpratt]

Successful merges:

• triagebot: add myself to libs rotation #155894 (triagebot: add myself to libs rotation)
• Add regression test for LLVM bug with huge stack frames #155897 (Add regression test for LLVM bug with huge stack frames)
• Refer to FnDef as "function item", not "function pointer" #155900 (Refer to FnDef as "function item", not "function pointer")

r? @ghost

Create a similar rollup

[jhpratt]

@bors r+ rollup=never p=5

[rust-bors]

📌 Commit 6960391 has been approved by jhpratt

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: jhpratt
Duration: 3h 18m 59s
Pushing b806d39 to main...

[rust-timer]

📌 Perf builds for each rolled up PR:

PR#	Message	Perf Build Sha
#155894	triagebot: add myself to libs rotation	1da1d31ab82c289b85c2d3ebdbd02738d2d844cd (link)
#155897	Add regression test for LLVM bug with huge stack frames	bc81c8b94a4e7a164165fdfbc06212d87c9ff7a1 (link)
#155900	Refer to FnDef as "function item", not "function pointer"	a2019f83c48eddad405752e9eded40315b9d9def (link)

previous master: b20956b0f4

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 b20956b (parent) -> b806d39 (this PR)

Test differences

Show 12 test diffs

Stage 1

• [ui] tests/ui/codegen/huge-stacks.rs#optimized: [missing] -> pass (J1)
• [ui] tests/ui/codegen/huge-stacks.rs#unoptimized: [missing] -> pass (J1)
• [ui] tests/ui/codegen/huge-stacks.rs#optimized: [missing] -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J3)
• [ui] tests/ui/codegen/huge-stacks.rs#unoptimized: [missing] -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J3)

Stage 2

• [ui] tests/ui/codegen/huge-stacks.rs#optimized: [missing] -> ignore (only executed when the pointer width is 64bit) (J0)
• [ui] tests/ui/codegen/huge-stacks.rs#unoptimized: [missing] -> ignore (only executed when the pointer width is 64bit) (J0)
• [ui] tests/ui/codegen/huge-stacks.rs#optimized: [missing] -> pass (J2)
• [ui] tests/ui/codegen/huge-stacks.rs#unoptimized: [missing] -> pass (J2)
• [ui] tests/ui/codegen/huge-stacks.rs#optimized: [missing] -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J4)
• [ui] tests/ui/codegen/huge-stacks.rs#unoptimized: [missing] -> ignore (ignored when the LLVM version 21.1.2 is older than 22.0.0) (J4)

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

Job group index

• J0: arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, i686-msvc-1, x86_64-gnu-llvm-22-2
• J1: x86_64-gnu-llvm-22-3
• J2: aarch64-apple, aarch64-gnu, aarch64-msvc-1, optional-x86_64-gnu-parallel-frontend, test-various, x86_64-gnu, x86_64-gnu-debug, x86_64-gnu-gcc, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1
• J3: x86_64-gnu-llvm-21-3
• J4: aarch64-gnu-llvm-21-1, x86_64-gnu-llvm-21, x86_64-gnu-llvm-21-2

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard b806d39f033b05ea5aec9a353df75314007a728c --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-aux: 1h 51m -> 2h 20m (+26.2%)
2. dist-ohos-x86_64: 1h 23m -> 1h 3m (-24.7%)
3. dist-powerpc-linux: 1h 14m -> 1h 30m (+21.8%)
4. x86_64-msvc-1: 2h 31m -> 2h 3m (-18.4%)
5. pr-check-1: 34m 38s -> 28m 23s (-18.0%)
6. test-various: 1h 39m -> 1h 55m (+16.1%)
7. armhf-gnu: 1h 39m -> 1h 24m (-15.2%)
8. x86_64-gnu-debug: 2h 4m -> 1h 47m (-13.8%)
9. x86_64-gnu-tools: 1h 3m -> 55m 18s (-13.6%)
10. x86_64-gnu-llvm-21-1: 1h 16m -> 1h 6m (-13.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 (b806d39): 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.2%	[-0.2%, -0.2%]	1
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (secondary -4.7%)

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)	-4.7%	[-7.3%, -2.1%]	2
All ❌✅ (primary)	-	-	0

Cycles

This perf run didn't have relevant results for this metric.

Binary size

Results (primary -0.1%, secondary -0.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)	-0.1%	[-0.2%, -0.0%]	49
Improvements ✅ (secondary)	-0.1%	[-0.2%, -0.0%]	23
All ❌✅ (primary)	-0.1%	[-0.2%, -0.0%]	49

Bootstrap: 489.569s -> 489.748s (0.04%)
Artifact size: 393.41 MiB -> 393.29 MiB (-0.03%)