Add f16 formatting and parsing by tgross35 · Pull Request #127013 · 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 4455c89 (parent) -> 4d051fb (this PR)

Test differences

Show 17 test diffs

Stage 0

• num::dec2flt::decimal::check_fast_path_f16: [missing] -> pass (J1)
• num::dec2flt:🛟:test_f16_consts: [missing] -> pass (J1)
• num::dec2flt:🛟:test_f16_integer_decode: [missing] -> pass (J1)
• num::dec2flt::lemire::compute_float_f16_rounding: [missing] -> pass (J1)
• num::flt2dec::random::exact_f16_random_equivalence_test: [missing] -> pass (J1)
• num::flt2dec::random::shortest_f16_exhaustive_equivalence_test: [missing] -> pass (J1)

Stage 1

• num::dec2flt::decimal::check_fast_path_f16: [missing] -> pass (J0)
• num::dec2flt:🛟:test_f16_consts: [missing] -> pass (J0)
• num::dec2flt:🛟:test_f16_integer_decode: [missing] -> pass (J0)
• num::dec2flt::lemire::compute_float_f16_rounding: [missing] -> pass (J0)
• num::flt2dec::random::exact_f16_random_equivalence_test: [missing] -> pass (J0)
• num::flt2dec::random::shortest_f16_exhaustive_equivalence_test: [missing] -> pass (J2)
• num::flt2dec::random::shortest_f16_exhaustive_equivalence_test: [missing] -> ignore (J3)

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

Job group index

• J0: 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-msvc-1
• J1: mingw-check
• J2: 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-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-msvc-1
• J3: x86_64-gnu-aux Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml --
test-dashboard 4d051fb306e661654d088892e02e69b8c0c39d43 --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. dist-aarch64-linux: 5276.3s -> 7698.3s (45.9%)
2. dist-x86_64-apple: 10179.7s -> 7488.0s (-26.4%)
3. x86_64-apple-2: 4891.2s -> 4440.8s (-9.2%)
4. aarch64-apple: 3815.6s -> 4158.7s (9.0%)
5. x86_64-apple-1: 7586.7s -> 6936.2s (-8.6%)
6. dist-apple-various: 5946.6s -> 6435.1s (8.2%)
7. x86_64-msvc-ext1: 7033.4s -> 7521.5s (6.9%)
8. i686-gnu-2: 6282.8s -> 6683.9s (6.4%)
9. x86_64-gnu-aux: 5838.3s -> 6206.0s (6.3%)
10. x86_64-gnu-llvm-20-2: 6240.9s -> 5852.2s (-6.2%) 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.