-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Inline try_get_cached #82197
Inline try_get_cached #82197
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 db36db2 with merge 47948b92152f8dec0cdf064a17c3f92f52e45543... |
☀️ Try build successful - checks-actions |
Queued 47948b92152f8dec0cdf064a17c3f92f52e45543 with parent 9d3deed, future comparison URL. |
Finished benchmarking try commit (47948b92152f8dec0cdf064a17c3f92f52e45543): 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 |
I guess we found the guilty party. |
📌 Commit db36db2 has been approved by |
⌛ Testing commit db36db2 with merge 381b13728edeb1d036b5f5c2e3547503bff2b74a... |
💔 Test failed - checks-actions |
Seems spurious? cc @rust-lang/infra @bors retry |
☀️ Test successful - checks-actions |
A job failed! Check out the build log: (web) (plain) Click to see the possible cause of the failure (guessed by this bot)
|
No description provided.