Run rustdoc tests in opt-dist tests

[Kobzol]

Context: #150287

try-job: dist-x86_64-linux

[Kobzol]

@bors try

[rust-bors]

☀️ Try build successful (CI)
Build commit: 4872b81 (4872b815ac3093154ffb956affe6951ff18e66fe, parent: ab32c26b49eacb1b694972bb29d20167bdbdfc51)

[Kobzol]

Running these tests takes ~20s, so it should be fine to just run them always.

r? @Urgau

[rustbot]

Some changes occurred in src/tools/opt-dist

cc @Kobzol

[Urgau]

Indeed, they only ~20s. https://triage.rust-lang.org/gha-logs/rust-lang/rust/59209398254#L2025-12-31T12:30:44.5062692Z-L2025-12-31T12:31:02.7405328Z

[Urgau]

Looks good to me. Thanks.

View changes since this review

[Urgau]

@bors r+ rollup

[bors]

📌 Commit 03d2bcc has been approved by Urgau

It is now in the queue for this repository.

[bors]

⌛ Testing commit 03d2bcc with merge 8a24a20...

[bors]

☀️ Test successful - checks-actions
Approved by: Urgau
Pushing 8a24a20 to main...

[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 bf6b5b9 (parent) -> 8a24a20 (this PR)

Test differences

Show 4 test diffs

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

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 8a24a202aa02f677fc2a3e0e1a69af7545803952 --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-aarch64-apple: 7415.9s -> 9354.3s (+26.1%)
2. dist-x86_64-solaris: 5094.8s -> 5960.6s (+17.0%)
3. aarch64-gnu-debug: 4362.3s -> 3716.4s (-14.8%)
4. x86_64-rust-for-linux: 3034.3s -> 2594.2s (-14.5%)
5. x86_64-gnu-tools: 3669.6s -> 3153.2s (-14.1%)
6. dist-x86_64-apple: 7628.1s -> 8684.9s (+13.9%)
7. x86_64-gnu-gcc: 3492.2s -> 3030.3s (-13.2%)
8. x86_64-gnu-llvm-20-1: 4344.2s -> 3789.7s (-12.8%)
9. dist-sparcv9-solaris: 5187.2s -> 5844.7s (+12.7%)
10. pr-check-1: 1871.0s -> 1634.1s (-12.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 (8a24a20): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

Results (secondary -2.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)	-2.7%	[-3.3%, -2.4%]	3
All ❌✅ (primary)	-	-	0

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 473.964s -> 473.485s (-0.10%)
Artifact size: 390.78 MiB -> 390.77 MiB (-0.00%)