rust (original) (raw)

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 4b27a04 (parent) -> ff223d3 (this PR)

Test differences

Show 13 test diffs

Stage 1

[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs: [missing] -> pass (J0)
[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs#other: ignore (ignored when the architecture is x86_64) -> [missing] (J0)
[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs#x86-32-sse2: ignore (only executed when the target rustc_abi is rustc_abi-x86-sse2) -> [missing] (J0)
[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs#x86-64: pass -> [missing] (J0)

Stage 2

[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs#other: ignore (ignored when the architecture is x86_64) -> [missing] (J1)
[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs#x86-64: pass -> [missing] (J1)
[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs#other: ignore (ignored when the target rustc_abi is rustc_abi-x86-sse2) -> [missing] (J2)
[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs#x86-32-sse2: pass -> [missing] (J2)
[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs#x86-64: ignore (only executed when the architecture is x86_64) -> [missing] (J3)
[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs: [missing] -> pass (J4)
[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs: [missing] -> ignore (ignored when the target is i686-pc-windows-msvc) (J5)
[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs#x86-32-sse2: ignore (only executed when the target rustc_abi is rustc_abi-x86-sse2) -> [missing] (J6)
[codegen] tests/codegen/simd-intrinsic/simd-intrinsic-transmute-array.rs#other: pass -> [missing] (J7)

Job group index

J0: x86_64-gnu-llvm-19-3, x86_64-gnu-llvm-20-3
J1: test-various, x86_64-apple-1, x86_64-gnu, x86_64-gnu-llvm-19-2, x86_64-gnu-llvm-20-2, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1
J2: dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, i686-msvc-1
J3: aarch64-apple, aarch64-gnu, arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, i686-msvc-1
J4: aarch64-apple, aarch64-gnu, arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, test-various, x86_64-apple-1, x86_64-gnu, x86_64-gnu-llvm-19-2, x86_64-gnu-llvm-20-2, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1
J5: i686-msvc-1
J6: aarch64-apple, aarch64-gnu, arm-android, armhf-gnu, test-various, x86_64-apple-1, x86_64-gnu, x86_64-gnu-llvm-19-2, x86_64-gnu-llvm-20-2, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1
J7: aarch64-apple, aarch64-gnu, arm-android, armhf-gnu Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml --
test-dashboard ff223d35cd684f8c7c07ed4b7fd4475e482359ab --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

dist-aarch64-linux: 8219.2s -> 5897.4s (-28.2%)
mingw-check-1: 1602.1s -> 1912.3s (19.4%)
x86_64-gnu-aux: 5266.5s -> 6091.7s (15.7%)
i686-gnu-2: 5444.5s -> 6097.1s (12.0%)
i686-gnu-1: 7187.9s -> 7972.8s (10.9%)
i686-gnu-nopt-1: 7240.1s -> 8023.8s (10.8%)
arm-android: 4815.9s -> 5302.6s (10.1%)
x86_64-rust-for-linux: 2301.0s -> 2519.8s (9.5%)
x86_64-gnu-llvm-20-2: 5550.0s -> 6034.0s (8.7%)
armhf-gnu: 3879.3s -> 4205.3s (8.4%) 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.