-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Update host LLVM to 20.1 on CI #137189
Update host LLVM to 20.1 on CI #137189
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Update host LLVM to 20.1 on CI r? `@ghost`
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (bf1902f): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowBenchmarking 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 may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (secondary 3.7%)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.
CyclesResults (primary -0.6%)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.
Binary sizeResults (secondary 0.0%)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.
Bootstrap: 774.698s -> 771.5s (-0.41%) |
Interesting, usually there are more perf. effects. r? @nikic (Let me know if you want to wait for the final release, last time we kind of forget and stayed on RC the whole time 😆) |
Staying on an rc for the host compiler isn't really a problem... @bors r+ |
Update host LLVM to 20.1 on CI r? `@ghost`
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Sounds spurious. @bors retry |
Update host LLVM to 20.1 on CI r? `@ghost`
💥 Test timed out |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Let's try again. @bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (0769736): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 770.934s -> 770.476s (-0.06%) |
As previously pointed out, this is actually quite small perf difference for an LLVM change @rustbot label: +perf-regression-triaged |
r? @ghost