Build rustc with assertions in `dist-alt` jobs

[Kobzol]

Revival of https://github.com/rust-lang/rust/pull/131077, to check CI times now that we don't do PGO/BOLT anymore on Linux -alt builds.

r? @ghost

try-job: dist-x86_64-msvc-alt try-job: dist-x86_64-linux-alt

[rustbot]

Some changes occurred in src/tools/opt-dist

cc @kobzol

[Kobzol]

@bors2 try

[rust-bors[bot]]

:hourglass: Trying commit fea114c5af774b07184d181da518fd5bd8df1dab with merge 719c0f0e93c1f3606edfa5381222b9d9b8b0c087…

To cancel the try build, run the command @bors2 try cancel.

[rust-bors[bot]]

:sunny: Try build successful (CI) Build commit: 719c0f0e93c1f3606edfa5381222b9d9b8b0c087 (719c0f0e93c1f3606edfa5381222b9d9b8b0c087)

[Kobzol]

@bors2 try

[rust-bors[bot]]

:hourglass: Trying commit 6d4df2d0210c40566435d1b63082cfc81005f2cb with merge 6acdc261c9a2a67217d87dea62949057a09f503f…

To cancel the try build, run the command @bors2 try cancel.

[rust-bors[bot]]

:sunny: Try build successful (CI) Build commit: 6acdc261c9a2a67217d87dea62949057a09f503f (6acdc261c9a2a67217d87dea62949057a09f503f)

[Kobzol]

2h 14 minutes with the 8-core runner, pretty nice. @marcoieni would you be fine to switch the dist-alt runner to 8 cores in order to get rustc assertions in CI builds?

[marcoieni]

2h 14 minutes with the 8-core runner, pretty nice. @marcoieni would you be fine to switch the dist-alt runner to 8 cores in order to get rustc assertions in CI builds?

yes it's fine 👍

[Kobzol]

@bors2 try

[rust-bors[bot]]

:hourglass: Trying commit 607a567916667bb6c944034aa4d2664e21d5fbe3 with merge 11c9e81093a637885ff88d565c318d0b9c074c63…

To cancel the try build, run the command @bors2 try cancel.

[rust-bors[bot]]

:sunny: Try build successful (CI) Build commit: 11c9e81093a637885ff88d565c318d0b9c074c63 (11c9e81093a637885ff88d565c318d0b9c074c63)

[Kobzol]

r? @marcoieni

[marcoieni]

@bors r+

[bors]

:pushpin: Commit 607a567916667bb6c944034aa4d2664e21d5fbe3 has been approved by marcoieni

It is now in the queue for this repository.

[workingjubilee]

sorry, I don't have a good reason, it just has a vibe, and I think everyone else is assuming it does too.

@bors rollup=iffy

[bors]

:hourglass: Testing commit 607a567916667bb6c944034aa4d2664e21d5fbe3 with merge 64c81fd10509924ca4da5d93d6052a65b75418a5...

[bors]

:sunny: Test successful - checks-actions Approved by: marcoieni Pushing 64c81fd10509924ca4da5d93d6052a65b75418a5 to master...

[github-actions[bot]]

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 d087f112b7d1323446c7b39a8b616aee7fa56b3d (parent) -> 64c81fd10509924ca4da5d93d6052a65b75418a5 (this PR)

Test differences

No test diffs found

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 64c81fd10509924ca4da5d93d6052a65b75418a5 --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-apple-2: 3428.9s -> 5893.1s (71.9%)
2. dist-x86_64-apple: 7706.6s -> 9773.4s (26.8%)
3. dist-x86_64-linux-alt: 9526.9s -> 7293.1s (-23.4%)
4. aarch64-apple: 4330.2s -> 5259.7s (21.5%)
5. dist-x86_64-msvc-alt: 7142.8s -> 8375.8s (17.3%)
6. aarch64-gnu-debug: 3575.9s -> 4064.3s (13.7%)
7. dist-arm-linux-gnueabi: 4555.5s -> 5160.7s (13.3%)
8. x86_64-apple-1: 6185.4s -> 6946.8s (12.3%)
9. i686-gnu-2: 5391.9s -> 6044.3s (12.1%)
10. mingw-check-1: 1677.9s -> 1860.1s (10.9%)

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 (64c81fd10509924ca4da5d93d6052a65b75418a5): 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)

Results (primary -2.6%, secondary -5.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)	-2.6%	[-3.6%, -1.6%]	2
Improvements ✅ (secondary)	-5.7%	[-8.2%, -3.3%]	2
All ❌✅ (primary)	-2.6%	[-3.6%, -1.6%]	2

Cycles

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

Binary size

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

Bootstrap: 757.156s -> 757.551s (0.05%) Artifact size: 372.29 MiB -> 372.30 MiB (0.00%)