Extending #[rustc_force_inline] to be applicable to inherent methods by CrooseGit · Pull Request #147231 · 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 5c7ae0c (parent) -> 8d603ef (this PR)
Test differences
Show 16 test diffs
Stage 1
[mir-opt] tests/mir-opt/inline/forced_closure_inherent.rs: [missing] -> pass (J1)[mir-opt] tests/mir-opt/inline/forced_inherent.rs: [missing] -> pass (J1)[mir-opt] tests/mir-opt/inline/forced_inherent_ambiguous.rs: [missing] -> pass (J1)[mir-opt] tests/mir-opt/inline/forced_inherent_async.rs: [missing] -> pass (J1)[mir-opt] tests/mir-opt/inline/forced_inherent_dead_code.rs: [missing] -> pass (J1)[ui] tests/ui/force-inlining/inherent.rs: [missing] -> pass (J1)
Stage 2
[mir-opt] tests/mir-opt/inline/forced_closure_inherent.rs: [missing] -> pass (J0)[mir-opt] tests/mir-opt/inline/forced_inherent.rs: [missing] -> pass (J0)[mir-opt] tests/mir-opt/inline/forced_inherent_ambiguous.rs: [missing] -> pass (J0)[mir-opt] tests/mir-opt/inline/forced_inherent_async.rs: [missing] -> pass (J0)[mir-opt] tests/mir-opt/inline/forced_inherent_dead_code.rs: [missing] -> pass (J0)[ui] tests/ui/force-inlining/inherent.rs: [missing] -> pass (J2)
Additionally, 4 doctest diffs were found. These are ignored, as they are noisy.
Job group index
- J0: aarch64-apple, aarch64-gnu, aarch64-gnu-llvm-20-1, aarch64-msvc-1, arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, i686-msvc-1, test-various, x86_64-gnu, x86_64-gnu-llvm-20, x86_64-gnu-llvm-20-2, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1
- J1: x86_64-gnu-llvm-20-3
- J2: aarch64-apple, aarch64-gnu, aarch64-gnu-llvm-20-1, aarch64-msvc-1, arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, i686-msvc-1, test-various, x86_64-gnu, x86_64-gnu-debug, x86_64-gnu-llvm-20, x86_64-gnu-llvm-20-2, 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 8d603ef2879fd263f8e9aea340b4c035ed7973db --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-apple-various: 4603.5s -> 3080.5s (-33.1%)
- aarch64-apple: 9443.1s -> 7500.9s (-20.6%)
- dist-x86_64-freebsd: 6227.8s -> 5023.6s (-19.3%)
- dist-i686-msvc: 7921.7s -> 9085.6s (14.7%)
- pr-check-1: 1385.2s -> 1571.7s (13.5%)
- x86_64-gnu-distcheck: 6188.6s -> 6945.8s (12.2%)
- x86_64-gnu-llvm-20-3: 6164.3s -> 6805.3s (10.4%)
- dist-aarch64-msvc: 6172.1s -> 5655.7s (-8.4%)
- dist-x86_64-mingw: 9296.5s -> 8578.9s (-7.7%)
- i686-msvc-2: 7751.9s -> 8346.8s (7.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.