Use dylib build in distcheck

[nikic]

This reduces disk usage, and thus avoids the distcheck job running out of disk space.

[nikic]

@bors try jobs=x86_64-gnu-distcheck

[rustbot]

r? @marcoieni

rustbot has assigned @marcoieni.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: infra-ci
• infra-ci expanded to Kobzol, Mark-Simulacrum, jdno, jieyouxu, marcoieni
• Random selection from Mark-Simulacrum, jdno, marcoieni

[rust-bors]

☀️ Try build successful (CI)
Build commit: d35299c (d35299c508333496160ae148947ff35b2a275d8d)
Base parent: 29e68fe (29e68fe2295f8fc2feb52b8cb0b61a055842fdcf)

[Kobzol]

@bors r+ p=1 note="unblock CI"

[rust-bors]

📌 Commit 1a4a07e has been approved by Kobzol

It is now in the queue for this repository.

[rust-bors]

💔 Test for 464b339 failed: CI. Failed job:

• auto - x86_64-msvc-ext2 (web logs, enhanced plaintext logs)

[rust-log-analyzer]

The job x86_64-msvc-ext2 failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[Kobzol]

@bors retry spurious error

[rust-bors]

☀️ Test successful - CI
Approved by: Kobzol
Duration: 3h 28m 17s
Pushing da86f4d 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 29e68fe (parent) -> da86f4d (this PR)

Test differences

Show 1 test diff

Stage 2

• [run-make] tests/run-make/compressed-debuginfo-zstd: ignore (ignored if LLVM wasn't build with zstd for ELF section compression or LLVM is not the default codegen backend) -> pass (J0)

Job group index

• J0: x86_64-gnu-nopt

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard da86f4d0726be475afbbffe40cb2f65741c51ad3 --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. x86_64-gnu-gcc-core-tests: 26m 19s -> 8m 5s (-69.3%)
2. dist-apple-various: 1h 19m -> 2h 3m (+55.3%)
3. pr-check-1: 45m 56s -> 21m 22s (-53.5%)
4. x86_64-gnu-llvm-22-1: 47m 28s -> 1h 12m (+51.9%)
5. x86_64-gnu: 2h 41m -> 1h 30m (-44.2%)
6. x86_64-gnu-miri: 1h 54m -> 1h 4m (-43.8%)
7. x86_64-gnu-gcc: 1h 26m -> 50m 19s (-42.1%)
8. x86_64-rust-for-linux: 1h 17m -> 44m 39s (-42.1%)
9. dist-android: 20m 41s -> 28m 45s (+39.0%)
10. dist-aarch64-linux: 2h 4m -> 2h 50m (+37.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 (da86f4d): 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)

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

Cycles

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

Binary size

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

Bootstrap: 488.104s -> 489.287s (0.24%)
Artifact size: 387.69 MiB -> 387.73 MiB (0.01%)