-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 depend on the stored value when trying to cache on disk. #90065
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit ac394fd29fd2ff2baabfff4cc8106c4d8fb15610 with merge 6845448cab449904cedade472114984aa6e99168... |
☀️ Try build successful - checks-actions |
Queued 6845448cab449904cedade472114984aa6e99168 with parent 1af55d1, future comparison URL. |
Finished benchmarking commit (6845448cab449904cedade472114984aa6e99168): comparison url. Summary: This benchmark run did not return any relevant changes. 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 |
@bors r+ |
📌 Commit ac394fd29fd2ff2baabfff4cc8106c4d8fb15610 has been approved by |
☔ The latest upstream changes (presumably #89978) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors r=Mark-Simulacrum |
📌 Commit 0a5666b has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (55ccbd0): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Having different criteria for loading and saving of query results can lead to saved results that may never be loaded.
Since the on-disk cache is discarded as soon as a compilation error is issued, there should not be any need for an exclusion mecanism based on errors.
As a result, the possibility to condition the storage on the value itself does not appear useful.