Update cargo submodule by weihanglo · Pull Request #149934 · 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 8188f6c (parent) -> 430d829 (this PR)

Test differences

Show 83 test diffs

Stage 2

Additionally, 4 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 430d8297c712ca7e8a4866d7ddccf1b71ba5d4d3 --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. x86_64-rust-for-linux: 3265.0s -> 2766.1s (-15.3%)
  2. x86_64-gnu-llvm-20: 2903.8s -> 2465.2s (-15.1%)
  3. dist-aarch64-llvm-mingw: 6362.7s -> 5438.7s (-14.5%)
  4. pr-check-1: 2008.5s -> 1728.5s (-13.9%)
  5. dist-aarch64-msvc: 5570.5s -> 6239.6s (+12.0%)
  6. dist-riscv64-linux: 4630.8s -> 5185.8s (+12.0%)
  7. x86_64-gnu-gcc: 3477.7s -> 3073.7s (-11.6%)
  8. x86_64-gnu-tools: 3707.4s -> 3303.2s (-10.9%)
  9. tidy: 166.2s -> 148.4s (-10.7%)
  10. dist-aarch64-apple: 6502.8s -> 5816.7s (-10.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.