Forbid freely casting lifetime bounds of dyn-types by BoxyUwU · Pull Request #136776 · 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 377656d (parent) -> 198328a (this PR)

Test differences

Show 8 test diffs

Stage 1

Stage 2

Additionally, 2 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 198328ad7960b1bece0dc48496bff6c62dd5d339 --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: 9788.8s -> 12314.1s (+25.8%)
  2. dist-apple-various: 4713.3s -> 3762.5s (-20.2%)
  3. dist-x86_64-apple: 6511.1s -> 7698.3s (+18.2%)
  4. dist-aarch64-apple: 9330.5s -> 7705.9s (-17.4%)
  5. dist-aarch64-llvm-mingw: 6251.2s -> 5275.2s (-15.6%)
  6. aarch64-gnu-debug: 4293.6s -> 4740.3s (+10.4%)
  7. aarch64-msvc-2: 4832.0s -> 5298.6s (+9.7%)
  8. x86_64-rust-for-linux: 2874.1s -> 3127.9s (+8.8%)
  9. i686-gnu-nopt-2: 8678.3s -> 7986.6s (-8.0%)
  10. x86_64-gnu-llvm-21-1: 3263.7s -> 3511.7s (+7.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.