Skip to content

Conversation

@weihanglo
Copy link
Member

7 commits in 5c0343317ce45d2ec17ecf41eaa473a02d73e29c..9fa462fe3a81e07e0bfdcc75c29d312c55113ebb
2025-11-18 19:05:44 +0000 to 2025-11-21 20:49:51 +0000

r? ghost

@rustbot
Copy link
Collaborator

rustbot commented Nov 21, 2025

Some changes occurred in src/tools/cargo

cc @ehuss

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Nov 21, 2025
@rustbot
Copy link
Collaborator

rustbot commented Nov 21, 2025

⚠️ Warning ⚠️

@weihanglo
Copy link
Member Author

@bors r+ rollup=never p=1

@bors
Copy link
Collaborator

bors commented Nov 22, 2025

📌 Commit e9440fb has been approved by weihanglo

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Nov 22, 2025
@bors
Copy link
Collaborator

bors commented Nov 22, 2025

⌛ Testing commit e9440fb with merge ea98522...

@bors
Copy link
Collaborator

bors commented Nov 22, 2025

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing ea98522 to main...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Nov 22, 2025
@bors bors merged commit ea98522 into rust-lang:main Nov 22, 2025
12 checks passed
@rustbot rustbot added this to the 1.93.0 milestone Nov 22, 2025
@github-actions
Copy link
Contributor

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 5934b06 (parent) -> ea98522 (this PR)

Test differences

Show 15 test diffs

Stage 2

  • artifact_dep::artifact_dep_target_does_not_propagate_to_deps_of_build_script: [missing] -> pass (J0)
  • artifact_dep::artifact_dep_target_does_not_propagate_to_proc_macro: [missing] -> pass (J0)
  • build_script_env::build_script_debug_assertions_build_override: [missing] -> pass (J0)
  • build_script_env::build_script_debug_assertions_dev: [missing] -> pass (J0)
  • build_script_env::build_script_debug_assertions_override_dev: [missing] -> pass (J0)
  • build_script_env::build_script_debug_assertions_override_release: [missing] -> pass (J0)
  • build_script_env::build_script_debug_assertions_release: [missing] -> pass (J0)
  • config_include::disallow_glob_syntax: [missing] -> pass (J0)
  • config_include::disallow_template_syntax: [missing] -> pass (J0)
  • config_include::nested_include_resolves_relative_to_including_file: [missing] -> pass (J0)
  • lto: [missing] -> ignore (requires nightly, CARGO_RUN_BUILD_STD_TESTS must be set) (J0)

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

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard ea98522531eec51ee51c393ea4a79af36469d696 --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: 10733.0s -> 7197.0s (-32.9%)
  2. x86_64-gnu-miri: 4742.9s -> 3953.6s (-16.6%)
  3. pr-check-1: 1966.5s -> 1670.5s (-15.1%)
  4. x86_64-gnu-debug: 7617.7s -> 6520.4s (-14.4%)
  5. i686-gnu-2: 6180.4s -> 5371.8s (-13.1%)
  6. x86_64-gnu-gcc: 3488.1s -> 3034.7s (-13.0%)
  7. x86_64-gnu-llvm-20: 2813.3s -> 2469.9s (-12.2%)
  8. armhf-gnu: 5322.3s -> 4743.2s (-10.9%)
  9. x86_64-gnu-llvm-21-2: 6149.1s -> 5490.7s (-10.7%)
  10. aarch64-gnu-debug: 4451.7s -> 3977.3s (-10.7%)
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.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (ea98522): comparison URL.

Overall result: ❌✅ regressions and improvements - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
0.5% [0.1%, 0.6%] 4
Improvements ✅
(primary)
-0.8% [-0.8%, -0.8%] 1
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -0.8% [-0.8%, -0.8%] 1

Max RSS (memory usage)

Results (primary 5.6%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
5.6% [5.6%, 5.6%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 5.6% [5.6%, 5.6%] 1

Cycles

Results (secondary 0.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
6.2% [6.2%, 6.2%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-6.1% [-6.1%, -6.1%] 1
All ❌✅ (primary) - - 0

Binary size

Results (primary 0.1%, secondary -0.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
0.1% [0.0%, 0.4%] 11
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.1% [-0.1%, -0.1%] 1
Improvements ✅
(secondary)
-0.1% [-0.1%, -0.1%] 2
All ❌✅ (primary) 0.1% [-0.1%, 0.4%] 12

Bootstrap: 470.656s -> 472.807s (0.46%)
Artifact size: 388.27 MiB -> 388.29 MiB (0.01%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants