improve c-variadic error reporting by folkertdev · Pull Request #146165 · 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 beeb8e3 (parent) -> 68baa87 (this PR)

Test differences

Show 7 test diffs

Stage 1

Stage 2

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

Job group index

Run

cargo run --manifest-path src/ci/citool/Cargo.toml --
test-dashboard 68baa87ba6f03f8b6af2a368690161f1601e4040 --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: 6734.4s -> 9954.8s (47.8%)
  2. dist-aarch64-apple: 6139.4s -> 7880.6s (28.4%)
  3. x86_64-gnu-llvm-20-3: 7055.4s -> 6329.0s (-10.3%)
  4. dist-various-1: 3689.4s -> 4011.2s (8.7%)
  5. dist-apple-various: 4138.6s -> 4453.4s (7.6%)
  6. dist-aarch64-msvc: 5493.4s -> 5855.5s (6.6%)
  7. x86_64-mingw-1: 10322.7s -> 9644.5s (-6.6%)
  8. dist-i686-linux: 6224.9s -> 6620.4s (6.4%)
  9. x86_64-mingw-2: 7539.3s -> 7998.2s (6.1%)
  10. dist-powerpc64le-linux-musl: 5185.5s -> 5473.8s (5.6%) 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.