Rollup of 3 pull requests

[JonathanBrouwer]

Successful merges:

• Add const_param_ty_unchecked gate #153536 (Add const_param_ty_unchecked gate)
• const-stabilize char::is_control() #155528 (const-stabilize char::is_control())
• VaList::next_arg: track_caller for better Miri errors #156086 (VaList::next_arg: track_caller for better Miri errors)

r? @ghost

Create a similar rollup

[JonathanBrouwer]

@bors r+ rollup=never p=5

[rust-bors]

📌 Commit 06354f4 has been approved by JonathanBrouwer

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 19m 42s
Pushing ad3a598 to main...

[rust-timer]

📌 Perf builds for each rolled up PR:

PR#	Message	Perf Build Sha
#153536	Add const_param_ty_unchecked gate	065d619fb04b9722cd567d201e5d75f3556f1d3e (link)
#155528	const-stabilize char::is_control()	3f909b7e2ad84e44db77781c8bd123dcaba44b3d (link)
#156086	VaList::next_arg: track_caller for better Miri errors	d1c15e0b95e458a950b22a253e14a7936b62f093 (link)

previous master: 818811b3cd

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 818811b (parent) -> ad3a598 (this PR)

Test differences

Show 161 test diffs

Stage 1

• [ui] tests/ui/const-generics/adt_const_params/const_param_ty_unchecked-unsupported.rs: [missing] -> pass (J1)
• [ui] tests/ui/const-generics/adt_const_params/const_param_ty_unchecked.rs: [missing] -> pass (J1)
• [ui] tests/ui/const-generics/adt_const_params/const_param_ty_unchecked_fail.rs: [missing] -> pass (J1)

Stage 2

• [ui] tests/ui/const-generics/adt_const_params/const_param_ty_unchecked-unsupported.rs: [missing] -> pass (J0)
• [ui] tests/ui/const-generics/adt_const_params/const_param_ty_unchecked.rs: [missing] -> pass (J0)
• [ui] tests/ui/const-generics/adt_const_params/const_param_ty_unchecked_fail.rs: [missing] -> pass (J0)

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

Job group index

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

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard ad3a598ca4bc7c68bcbbce3e0d3be9a7618df190 --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. i686-gnu-nopt-1: 1h 37m -> 2h 10m (+34.6%)
2. x86_64-gnu: 1h 49m -> 2h 23m (+30.2%)
3. pr-check-1: 27m 55s -> 35m 20s (+26.6%)
4. dist-x86_64-apple: 1h 36m -> 1h 59m (+24.2%)
5. dist-powerpc64le-linux-musl: 1h 15m -> 1h 33m (+23.8%)
6. dist-x86_64-msvc-alt: 2h 52m -> 2h 12m (-23.1%)
7. dist-powerpc64le-linux-gnu: 1h 17m -> 1h 34m (+21.7%)
8. dist-armv7-linux: 1h 14m -> 1h 30m (+20.8%)
9. dist-s390x-linux: 1h 29m -> 1h 11m (-19.9%)
10. dist-armhf-linux: 1h 27m -> 1h 11m (-18.1%)

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 (ad3a598): comparison URL.

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

Max RSS (memory usage)

Results (secondary -2.9%)

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)	-2.9%	[-7.8%, -0.5%]	5
All ❌✅ (primary)	-	-	0

Cycles

Results (secondary 1.2%)

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

Binary size

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

Bootstrap: 493.646s -> 495.343s (0.34%)
Artifact size: 394.40 MiB -> 394.42 MiB (0.01%)