Run main rust-analyzer tests in rust-lang/rust CI by jieyouxu · Pull Request #147372 · 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 ce63e5d (parent) -> eb171a2 (this PR)

Test differences

Show 15001 test diffs

Stage 0

Stage 1

(and 14838 additional test diffs)

Additionally, 63 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 eb171a227f9e5de5d376b6edb56b174bc8235fb3 --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. aarch64-apple: 8697.0s -> 15116.9s (+73.8%)
  2. aarch64-gnu-llvm-20-2: 2165.6s -> 2949.3s (+36.2%)
  3. x86_64-gnu-llvm-21-1: 3167.6s -> 4229.1s (+33.5%)
  4. x86_64-msvc-2: 7256.8s -> 9095.2s (+25.3%)
  5. x86_64-gnu-llvm-20-1: 3209.5s -> 3988.4s (+24.3%)
  6. aarch64-msvc-2: 5223.0s -> 6112.4s (+17.0%)
  7. x86_64-gnu-nopt: 7388.3s -> 8510.0s (+15.2%)
  8. x86_64-gnu-distcheck: 7046.4s -> 8051.0s (+14.3%)
  9. aarch64-gnu: 6443.9s -> 7352.3s (+14.1%)
  10. x86_64-gnu-llvm-21-2: 5653.0s -> 4868.8s (-13.9%) 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.