Rollup of 3 pull requests

[jhpratt]

Successful merges:

• fix: clarify that fs::rename on unix accepts targets that don't exist #149267 (fix: clarify that fs::rename on unix accepts targets that don't exist)
• Expand diagnostic for attributes on macro calls #158106 (Expand diagnostic for attributes on macro calls)
• add a test for the getrandom fallback #158125 (add a test for the getrandom fallback)

r? @ghost

Create a similar rollup

[jhpratt]

@bors r+ rollup=never p=5

[rust-bors]

📌 Commit 82b925e has been approved by jhpratt

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: jhpratt
Duration: 3h 13m 53s
Pushing 32ea361 to main...

[rust-timer]

📌 Perf builds for each rolled up PR:

PR#	Message	Perf Build Sha
#149267	fix: clarify that fs::rename on unix accepts targets that d…	14ee7260aeb56314843ab6106fa32cd0ebe1437a (link)
#158106	Expand diagnostic for attributes on macro calls	ec7b4a65e4c280f8bfe6f9dbf04fcba0a14cbb68 (link)
#158125	add a test for the getrandom fallback	8b721e1c51e89811e2f6f91d3582df3aeeb3d1ac (link)

previous master: f428d123ab

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 f428d12 (parent) -> 32ea361 (this PR)

Test differences

Show 74 test diffs

Stage 1

• [ui] tests/ui/std/linux-getrandom-fallback.rs: [missing] -> pass (J0)
• [ui (polonius)] tests/ui/std/linux-getrandom-fallback.rs: [missing] -> pass (J1)

Stage 2

• [ui] tests/ui/std/linux-getrandom-fallback.rs: [missing] -> pass (J2)
• [ui] tests/ui/std/linux-getrandom-fallback.rs: [missing] -> ignore (only executed when the operating system is linux) (J3)

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

Job group index

• J0: x86_64-gnu-llvm-21-3, x86_64-gnu-llvm-22-3, x86_64-gnu-next-trait-solver-polonius
• J1: x86_64-gnu-next-trait-solver-polonius
• J2: aarch64-gnu, aarch64-gnu-llvm-21-1, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-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
• J3: aarch64-apple, aarch64-apple-macos-26, aarch64-msvc-1, arm-android, i686-msvc-1, x86_64-mingw-1, x86_64-msvc-1

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 32ea3615cc027bcb8fd720c7511ffb484f6223a3 --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-i686-msvc: 1h 17m -> 2h 9m (+67.5%)
2. dist-powerpc64le-linux-musl: 1h 8m -> 1h 33m (+37.4%)
3. x86_64-msvc-ext2: 1h 24m -> 1h 54m (+34.7%)
4. dist-i686-mingw: 2h 5m -> 2h 44m (+31.1%)
5. x86_64-gnu-next-trait-solver-polonius: 58m 59s -> 42m 22s (-28.2%)
6. dist-i686-linux: 1h 24m -> 1h 43m (+23.5%)
7. dist-x86_64-llvm-mingw: 1h 59m -> 1h 31m (-23.1%)
8. dist-ohos-aarch64: 1h 18m -> 1h 1m (-21.5%)
9. x86_64-gnu-nopt: 1h 51m -> 2h 14m (+20.6%)
10. dist-x86_64-solaris: 1h 16m -> 1h 31m (+19.7%)

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

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

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

Max RSS (memory usage)

Results (primary 5.1%)

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

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

Cycles

Results (primary -4.7%, 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)	-4.7%	[-17.3%, -1.4%]	38
Improvements ✅ (secondary)	-4.7%	[-16.9%, -2.0%]	17
All ❌✅ (primary)	-4.7%	[-17.3%, -1.4%]	38

Binary size

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

Bootstrap: 482.643s -> 489.308s (1.38%)
Artifact size: 391.20 MiB -> 390.69 MiB (-0.13%)