-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
[WIP] Always use EvaluatedToOkModuloRegions
instead of EvaluatedToOk
#83719
Conversation
r? @varkor (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 62f17a7 with merge 11ca0937602153d3b98cda098d23d95df5c59a56... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Try build successful - checks-actions |
Queued 11ca0937602153d3b98cda098d23d95df5c59a56 with parent a5029ac, future comparison URL. |
Finished benchmarking try commit (11ca0937602153d3b98cda098d23d95df5c59a56): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
Regressions up to 33%, with many benchmarks regressing 1-10% |
The 33% regression is a doc build I think; I count 10 cases over 3% and 27 cases over 1%. So not ideal but still perfectly sufficient for a temporary solution? |
Superseded by #85186 |
No description provided.