Rollup of 5 pull requests

[Zalathar]

Successful merges:

• Replace try_reserve_exact with try_with_capacity in std::fs::read #141211 (Replace try_reserve_exact with try_with_capacity in std::fs::read)
• trim cache module in utils bootstrap #141257 (trim cache module in utils bootstrap)
• Update books #141259 (Update books)
• current_dll_path: fix mistake in assertion message #141261 (current_dll_path: fix mistake in assertion message)
• Properly remove Noratrieb from review rotation #141262 (Properly remove Noratrieb from review rotation)

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[Zalathar]

@bors r+ rollup=never p=5

[bors]

📌 Commit 4a47234 has been approved by Zalathar

It is now in the queue for this repository.

[bors]

⌛ Testing commit 4a47234 with merge a8e4c68...

[bors]

☀️ Test successful - checks-actions
Approved by: Zalathar
Pushing a8e4c68 to master...

[rust-timer]

📌 Perf builds for each rolled up PR:

PR#	Message	Perf Build Sha
#141211	Replace try_reserve_exact with try_with_capacity in `st…	a5c5395c0a97afec0d4a9ad048682e558950f212 (link)
#141257	trim cache module in utils bootstrap	5897dc2f2d3547b3eaa0b10cc4dba2a2f3c3c4da (link)
#141259	Update books	4e69f24b3fb1a15d82c4670ba121b6b88a9768fc (link)
#141261	current_dll_path: fix mistake in assertion message	cefc0daaa8a6e0b679a5acddcbef34dcfe13200a (link)
#141262	Properly remove Noratrieb from review rotation	dd84ace92a35e80cb160bd1e5823b5e1c73cec70 (link)

previous master: 60dabef95a

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 60dabef (parent) -> a8e4c68 (this PR)

Test differences

Show 272 test diffs

Stage 0

• utils::cache::tests::test_path_interning: pass -> [missing] (J0)
• utils::cache::tests::test_vec_interning: pass -> [missing] (J0)

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

Job group index

• J0: aarch64-apple, aarch64-gnu, i686-gnu-2, i686-gnu-nopt-2, i686-msvc-2, x86_64-apple-1, x86_64-gnu, x86_64-gnu-llvm-19-3, x86_64-gnu-llvm-20-3, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-2, x86_64-msvc-2

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard a8e4c68dcb4dc1e48a0db294c5323cab0227fcb9 --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-apple-various: 5433.2s -> 7229.0s (33.1%)
2. dist-aarch64-linux: 7770.4s -> 5268.1s (-32.2%)
3. x86_64-msvc-1: 8224.1s -> 9994.1s (21.5%)
4. x86_64-apple-2: 6262.4s -> 4937.1s (-21.2%)
5. dist-x86_64-apple: 10868.2s -> 8696.5s (-20.0%)
6. dist-aarch64-apple: 6093.3s -> 5276.9s (-13.4%)
7. aarch64-apple: 4220.8s -> 4704.3s (11.5%)
8. dist-android: 2450.9s -> 2724.3s (11.2%)
9. x86_64-apple-1: 9297.2s -> 8379.4s (-9.9%)
10. x86_64-gnu-llvm-20-3: 6669.3s -> 7168.2s (7.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 (a8e4c68): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

This is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-1.5%	[-2.8%, -1.1%]	5
Improvements ✅ (secondary)	-1.0%	[-1.0%, -1.0%]	1
All ❌✅ (primary)	-1.5%	[-2.8%, -1.1%]	5

Max RSS (memory usage)

Results (primary -5.0%, secondary -1.9%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	0.4%	[0.4%, 0.5%]	3
Improvements ✅ (primary)	-5.0%	[-5.0%, -5.0%]	1
Improvements ✅ (secondary)	-5.5%	[-6.7%, -4.2%]	2
All ❌✅ (primary)	-5.0%	[-5.0%, -5.0%]	1

Cycles

Results (primary -2.8%, secondary 0.8%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	1.5%	[0.4%, 2.1%]	4
Improvements ✅ (primary)	-2.8%	[-2.8%, -2.8%]	1
Improvements ✅ (secondary)	-0.5%	[-0.5%, -0.5%]	2
All ❌✅ (primary)	-2.8%	[-2.8%, -2.8%]	1

Binary size

Results (primary -1.1%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

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

Bootstrap: 775.977s -> 776.444s (0.06%)
Artifact size: 365.61 MiB -> 365.63 MiB (0.01%)