-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: update rustc-perf
version used in CI and also the corresponding PGO benchmarks
#95724
Conversation
r? @kennytm (rust-highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 4a31a7ddcea8fe9805c3e5ec109cfa7dd98dc49c with merge 4e588bd7921c625cbd174d36019b756c3f4a89e7... |
This comment has been minimized.
This comment has been minimized.
4a31a7d
to
7865285
Compare
@bors try |
⌛ Trying commit 78652850eee351a42819ebb16408e0e23189186d with merge eeb04f75b8aca0f9a59de245b827af8601417357... |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
7865285
to
87b417e
Compare
@bors try |
⌛ Trying commit 87b417e9b5009aa34a5a7880c99f79bdae125981 with merge acb059f589ddb9e518c7a0afe86f34b8b5fbff6b... |
☀️ Try build successful - checks-actions |
Queued acb059f589ddb9e518c7a0afe86f34b8b5fbff6b with parent ce1a813, future comparison URL. |
Finished benchmarking commit (acb059f589ddb9e518c7a0afe86f34b8b5fbff6b): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf. @bors rollup=never Footnotes |
Results look rather good, slight upgrades in most benchmarks. Since we now want to optimize for the benchmarks in r? @nnethercote |
99bebd1
to
49efa23
Compare
@bors r+ |
📌 Commit 49efa23 has been approved by |
⌛ Testing commit 49efa23 with merge 051ddcc0cb2111e36d52105f0c3d60dc7a63b5c1... |
💔 Test failed - checks-actions |
@bors retry weird failure on dist-apple-various, no apparent error retrying once to see if it's a fluke |
⌛ Testing commit 49efa23 with merge 4aa34e17b4eae914cfe2b717b97388515fb8681d... |
💔 Test failed - checks-actions |
That.. looks spurious again? |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Test successful - checks-actions |
Finished benchmarking commit (399dd80): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
The old version was from May 2021. The
rustc-perf
benchmarks have seen a significant overhaul recently, so let's see if the new benchmarks can improve PGO performance.