Rename cfg_match! to cfg_select! by tgross35 · Pull Request #137198 · rust-lang/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 5df0f72 (parent) -> 6eef33b (this PR)

Test differences

Show 28 test diffs

Stage 0

• macros::cfg_match_basic: pass -> [missing] (J0)
• macros::cfg_match_debug_assertions: pass -> [missing] (J0)
• macros::cfg_match_no_duplication_on_64: pass -> [missing] (J0)
• macros::cfg_match_options: pass -> [missing] (J0)
• macros::cfg_match_two_functions: pass -> [missing] (J0)
• macros::cfg_select_basic: [missing] -> pass (J0)
• macros::cfg_select_debug_assertions: [missing] -> pass (J0)
• macros::cfg_select_no_duplication_on_64: [missing] -> pass (J0)
• macros::cfg_select_options: [missing] -> pass (J0)
• macros::cfg_select_two_functions: [missing] -> pass (J0)

Stage 1

• macros::cfg_match_basic: pass -> [missing] (J1)
• macros::cfg_match_debug_assertions: pass -> [missing] (J1)
• macros::cfg_match_options: pass -> [missing] (J1)
• macros::cfg_match_two_functions: pass -> [missing] (J1)
• macros::cfg_select_basic: [missing] -> pass (J1)
• macros::cfg_select_debug_assertions: [missing] -> pass (J1)
• macros::cfg_select_options: [missing] -> pass (J1)
• macros::cfg_select_two_functions: [missing] -> pass (J1)
• macros::cfg_match_no_duplication_on_64: pass -> [missing] (J2)
• macros::cfg_select_no_duplication_on_64: [missing] -> pass (J2)

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

Job group index

• J0: mingw-check
• J1: aarch64-apple, aarch64-gnu, arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, i686-msvc-1, test-various, x86_64-apple-1, x86_64-gnu, x86_64-gnu-aux, x86_64-gnu-llvm-19-1, x86_64-gnu-llvm-19-2, x86_64-gnu-llvm-19-3, x86_64-gnu-llvm-20-1, x86_64-gnu-llvm-20-2, x86_64-gnu-llvm-20-3, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1
• J2: aarch64-apple, aarch64-gnu, test-various, x86_64-apple-1, x86_64-gnu, x86_64-gnu-aux, x86_64-gnu-llvm-19-1, x86_64-gnu-llvm-19-2, x86_64-gnu-llvm-19-3, x86_64-gnu-llvm-20-1, x86_64-gnu-llvm-20-2, x86_64-gnu-llvm-20-3, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1 Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml --
test-dashboard 6eef33bb399cabfab16aa4e0825895f5f32f4e26 --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: 4888.6s -> 5807.5s (18.8%)
2. aarch64-apple: 5119.1s -> 4287.7s (-16.2%)
3. dist-apple-various: 6446.4s -> 7217.2s (12.0%)
4. dist-x86_64-msvc-alt: 7405.5s -> 8228.3s (11.1%)
5. dist-aarch64-apple: 5421.3s -> 5952.6s (9.8%)
6. x86_64-apple-1: 8252.9s -> 8782.1s (6.4%)
7. armhf-gnu: 4421.9s -> 4698.2s (6.2%)
8. dist-x86_64-musl: 7160.2s -> 7516.8s (5.0%)
9. dist-x86_64-apple: 8737.7s -> 9150.5s (4.7%)
10. x86_64-mingw-2: 7376.8s -> 7050.0s (-4.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.