Skip to content

Conversation

BoxyUwU
Copy link
Member

@BoxyUwU BoxyUwU commented Mar 28, 2025

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-release Relevant to the release subteam, which will review and decide on the PR/issue. labels Mar 28, 2025
@BoxyUwU
Copy link
Member Author

BoxyUwU commented Mar 28, 2025

@bors r+ rollup=never

@bors
Copy link
Collaborator

bors commented Mar 28, 2025

📌 Commit 9300fa1 has been approved by BoxyUwU

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 Mar 28, 2025
@bors
Copy link
Collaborator

bors commented Mar 29, 2025

⌛ Testing commit 9300fa1 with merge 928468c...

@bors
Copy link
Collaborator

bors commented Mar 29, 2025

☀️ Test successful - checks-actions
Approved by: BoxyUwU
Pushing 928468c to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Mar 29, 2025
@bors bors merged commit 928468c into rust-lang:master Mar 29, 2025
7 checks passed
@rustbot rustbot added this to the 1.88.0 milestone Mar 29, 2025
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 2848101 (parent) -> 928468c (this PR)

Test differences

No test diffs found

Job duration changes

  1. aarch64-gnu-debug: 4193.2s -> 5977.8s (42.6%)
  2. aarch64-gnu: 9375.6s -> 11000.7s (17.3%)
  3. dist-aarch64-apple: 4946.4s -> 5748.2s (16.2%)
  4. dist-x86_64-illumos: 5675.1s -> 6043.1s (6.5%)
  5. dist-apple-various: 6761.7s -> 7107.3s (5.1%)
  6. dist-x86_64-freebsd: 4739.9s -> 4969.2s (4.8%)
  7. x86_64-msvc-ext1: 7313.3s -> 7650.8s (4.6%)
  8. dist-armhf-linux: 5193.6s -> 5417.8s (4.3%)
  9. dist-x86_64-musl: 7250.6s -> 7534.5s (3.9%)
  10. x86_64-mingw-1: 8634.2s -> 8960.9s (3.8%)
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 (928468c): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results (primary 3.4%, secondary 0.8%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

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

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 778.59s -> 777.895s (-0.09%)
Artifact size: 365.95 MiB -> 365.92 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. T-release Relevant to the release subteam, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants