Fix span note for question mark expression by chenyukang · Pull Request #149442 · 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 95a27ad (parent) -> 31010ca (this PR)

Test differences

Show 5 test diffs

Stage 1

• [ui] tests/ui/traits/question-mark-span-144304.rs: [missing] -> pass (J1)

Stage 2

• [ui] tests/ui/traits/question-mark-span-144304.rs: [missing] -> pass (J0)
• [ui] tests/ui/traits/question-mark-span-144304.rs: [missing] -> ignore (ignored when the architecture is arm (armhf-gnu have more types implement trait From<T>, let's skip it)) (J2)

Additionally, 2 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, 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-gcc, x86_64-gnu-llvm-20, x86_64-gnu-llvm-20-2, x86_64-gnu-llvm-21-2, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1
• J1: x86_64-gnu-llvm-20-3, x86_64-gnu-llvm-21-3
• J2: arm-android, armhf-gnu Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml --
test-dashboard 31010ca61c3ff019e1480dda0a7ef16bd2bd51c0 --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-x86_64-apple: 6997.4s -> 10149.6s (+45.0%)
2. aarch64-apple: 10788.9s -> 12648.5s (+17.2%)
3. dist-x86_64-llvm-mingw: 7387.7s -> 8292.1s (+12.2%)
4. dist-x86_64-solaris: 5016.9s -> 5510.0s (+9.8%)
5. dist-android: 1527.1s -> 1671.5s (+9.5%)
6. dist-apple-various: 3854.4s -> 4216.0s (+9.4%)
7. dist-x86_64-netbsd: 4885.2s -> 5302.5s (+8.5%)
8. dist-ohos-x86_64: 4200.6s -> 4501.4s (+7.2%)
9. x86_64-gnu-miri: 5105.1s -> 4749.5s (-7.0%)
10. x86_64-rust-for-linux: 3175.6s -> 2960.6s (-6.8%) 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.