Rollup of 4 pull requests

[matthiaskrgr]

Successful merges:

• std: move kernel_copy to sys #147077 (std: move kernel_copy to sys)
• doc: fix strict_provenance_lints tracking issue link #149030 (doc: fix strict_provenance_lints tracking issue link)
• Update books #149031 (Update books)
• update my email in mailmap #149034 (update my email in mailmap)

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[matthiaskrgr]

@bors r+ rollup=never p=5

[bors]

📌 Commit d810867 has been approved by matthiaskrgr

It is now in the queue for this repository.

[bors]

⌛ Testing commit d810867 with merge fb505a7...

[bors]

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing fb505a7 to main...

[rust-timer]

📌 Perf builds for each rolled up PR:

PR#	Message	Perf Build Sha
#147077	std: move kernel_copy to sys	b94d0f6caebae05c2eb23098d734c3b5c6f83165 (link)
#149030	doc: fix strict_provenance_lints tracking issue link	d2099190d2ccc15517669c10e01458e85804b8d0 (link)
#149031	Update books	225c55e21337ed887a6d13bdca0dec3fb65e9331 (link)
#149034	update my email in mailmap	6d1f292b373e024b4cf523cae7ac1820d5a7f619 (link)

previous master: 0df64c5784

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 0df64c5 (parent) -> fb505a7 (this PR)

Test differences

Show 34 test diffs

Stage 1

• sys::io::kernel_copy::linux::tests::bench_file_to_file_copy: [missing] -> pass (J1)
• sys::io::kernel_copy::linux::tests::bench_file_to_socket_copy: [missing] -> pass (J1)
• sys::io::kernel_copy::linux::tests::bench_file_to_uds_copy: [missing] -> pass (J1)
• sys::io::kernel_copy::linux::tests::bench_socket_pipe_socket_copy: [missing] -> pass (J1)
• sys::io::kernel_copy::linux::tests::copies_append_mode_sink: [missing] -> pass (J1)
• sys::io::kernel_copy::linux::tests::copy_specialization: [missing] -> pass (J1)
• sys::io::kernel_copy::linux::tests::dont_splice_pipes_from_files: [missing] -> pass (J1)
• sys::pal::unix::kernel_copy::tests::bench_file_to_file_copy: pass -> [missing] (J1)
• sys::pal::unix::kernel_copy::tests::bench_file_to_socket_copy: pass -> [missing] (J1)
• sys::pal::unix::kernel_copy::tests::bench_file_to_uds_copy: pass -> [missing] (J1)
• sys::pal::unix::kernel_copy::tests::bench_socket_pipe_socket_copy: pass -> [missing] (J1)
• sys::pal::unix::kernel_copy::tests::copies_append_mode_sink: pass -> [missing] (J1)
• sys::pal::unix::kernel_copy::tests::copy_specialization: pass -> [missing] (J1)
• sys::pal::unix::kernel_copy::tests::dont_splice_pipes_from_files: pass -> [missing] (J1)

Stage 2

• sys::io::kernel_copy::linux::tests::bench_file_to_file_copy: [missing] -> pass (J0)
• sys::io::kernel_copy::linux::tests::bench_file_to_socket_copy: [missing] -> pass (J0)
• sys::io::kernel_copy::linux::tests::bench_file_to_uds_copy: [missing] -> pass (J0)
• sys::io::kernel_copy::linux::tests::bench_socket_pipe_socket_copy: [missing] -> pass (J0)
• sys::io::kernel_copy::linux::tests::copies_append_mode_sink: [missing] -> pass (J0)
• sys::io::kernel_copy::linux::tests::copy_specialization: [missing] -> pass (J0)
• sys::io::kernel_copy::linux::tests::dont_splice_pipes_from_files: [missing] -> pass (J0)
• sys::pal::unix::kernel_copy::tests::bench_file_to_file_copy: pass -> [missing] (J0)
• sys::pal::unix::kernel_copy::tests::bench_file_to_socket_copy: pass -> [missing] (J0)
• sys::pal::unix::kernel_copy::tests::bench_file_to_uds_copy: pass -> [missing] (J0)
• sys::pal::unix::kernel_copy::tests::bench_socket_pipe_socket_copy: pass -> [missing] (J0)
• sys::pal::unix::kernel_copy::tests::copies_append_mode_sink: pass -> [missing] (J0)
• sys::pal::unix::kernel_copy::tests::copy_specialization: pass -> [missing] (J0)
• sys::pal::unix::kernel_copy::tests::dont_splice_pipes_from_files: pass -> [missing] (J0)

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

Job group index

• J0: aarch64-gnu, aarch64-gnu-llvm-20-1, arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, test-various, x86_64-gnu, x86_64-gnu-llvm-20-2, x86_64-gnu-llvm-21-2, x86_64-gnu-nopt, x86_64-gnu-stable
• J1: i686-gnu-nopt-2, pr-check-2, x86_64-gnu-llvm-20-3, x86_64-gnu-llvm-21-3, x86_64-gnu-nopt

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \ test-dashboard fb505a798514a40569441110b44444d20a8bdb16 --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. aarch64-apple: 9224.3s -> 6413.8s (-30.5%)
2. dist-aarch64-apple: 5410.0s -> 6786.2s (+25.4%)
3. dist-aarch64-msvc: 6532.8s -> 5543.0s (-15.2%)
4. x86_64-rust-for-linux: 2905.2s -> 2479.3s (-14.7%)
5. pr-check-1: 1893.8s -> 1680.2s (-11.3%)
6. dist-apple-various: 4556.7s -> 4072.1s (-10.6%)
7. x86_64-gnu-llvm-20: 2679.6s -> 2399.1s (-10.5%)
8. dist-arm-linux-gnueabi: 4615.7s -> 5096.2s (+10.4%)
9. aarch64-gnu-llvm-20-1: 3786.2s -> 3406.1s (-10.0%)
10. x86_64-gnu: 7432.8s -> 6720.9s (-9.6%)

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 (fb505a7): 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
Regressions ❌ (secondary)	0.5%	[0.1%, 0.9%]	4
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary -5.0%)

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

Cycles

Results (secondary 3.8%)

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.8%	[3.7%, 4.0%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Binary size

Results (primary 0.0%)

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

	mean	range	count
Regressions ❌ (primary)	0.1%	[0.1%, 0.1%]	3
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-0.1%	[-0.1%, -0.1%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.0%	[-0.1%, 0.1%]	4

Bootstrap: 475.971s -> 475.249s (-0.15%)
Artifact size: 388.69 MiB -> 388.68 MiB (-0.00%)