Skip to content

Bump version to 1.73#113485

Merged
bors merged 1 commit intorust-lang:masterfrom
Mark-Simulacrum:bump-version
Jul 9, 2023
Merged

Bump version to 1.73#113485
bors merged 1 commit intorust-lang:masterfrom
Mark-Simulacrum:bump-version

Conversation

@Mark-Simulacrum
Copy link
Copy Markdown
Member

@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 Jul 8, 2023
@Mark-Simulacrum
Copy link
Copy Markdown
Member Author

@bors r+ rollup=never p=1

@bors
Copy link
Copy Markdown
Collaborator

bors commented Jul 8, 2023

📌 Commit 8a08a29 has been approved by Mark-Simulacrum

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 Jul 8, 2023
@bors
Copy link
Copy Markdown
Collaborator

bors commented Jul 9, 2023

⌛ Testing commit 8a08a29 with merge 03247fb...

@bors
Copy link
Copy Markdown
Collaborator

bors commented Jul 9, 2023

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing 03247fb to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jul 9, 2023
@bors bors merged commit 03247fb into rust-lang:master Jul 9, 2023
@rustbot rustbot added this to the 1.73.0 milestone Jul 9, 2023
@rust-timer
Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (03247fb): comparison URL.

Overall result: ❌ regressions - ACTION NEEDED

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
0.8% [0.5%, 1.2%] 32
Regressions ❌
(secondary)
0.7% [0.7%, 0.7%] 3
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.8% [0.5%, 1.2%] 32

Max RSS (memory usage)

Results

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)
- - 0
Regressions ❌
(secondary)
2.1% [2.1%, 2.1%] 2
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-2.5% [-3.2%, -1.9%] 2
All ❌✅ (primary) - - 0

Cycles

Results

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.8% [1.1%, 5.4%] 8
Regressions ❌
(secondary)
2.2% [1.2%, 3.5%] 8
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 3.8% [1.1%, 5.4%] 8

Binary size

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

Bootstrap: 655.503s -> 655.53s (0.00%)

@rustbot rustbot added the perf-regression Performance regression. label Jul 9, 2023
@lqd
Copy link
Copy Markdown
Member

lqd commented Jul 9, 2023

Unfortunate, but at least we see some of the noise we can sometimes reach... This has basically returned to normal in #112235 (comment)

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. perf-regression Performance regression. 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.

5 participants