-
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
Do not require the DefPathTable to construct the on-disk cache. #86150
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit aeb050d with merge 96aeb2380405b6f6544cc66cf76ba8915b13aefe... |
☀️ Try build successful - checks-actions |
Queued 96aeb2380405b6f6544cc66cf76ba8915b13aefe with parent a50d721, future comparison URL. |
Finished benchmarking try commit (96aeb2380405b6f6544cc66cf76ba8915b13aefe): 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 |
📌 Commit aeb050d has been approved by |
☀️ Test successful - checks-actions |
r? @michaelwoerister