-
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
incr.comp.: Fix potential unstable Fingerprint error for BorrowCheckResult #98924
incr.comp.: Fix potential unstable Fingerprint error for BorrowCheckResult #98924
Conversation
@bors try so we can the CI artifacts on the other issues |
⌛ Trying commit 9421219 with merge 3d838c809141fd15465b18559757a34c360c11d4... |
☀️ Try build successful - checks-actions |
r=me once you've performed any additional testing with the CI artifact toolchain. |
@rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
@rust-timer build 3d838c809141fd15465b18559757a34c360c11d4 |
Queued 3d838c809141fd15465b18559757a34c360c11d4 with parent 4045ce6, future comparison URL. |
Finished benchmarking commit (3d838c809141fd15465b18559757a34c360c11d4): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
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 may lead to changes in compiler perf. @bors rollup=never Footnotes |
@bors r=Aaron1011 #98959 probably fixes the underlying source of indeterminism, but this PR doesn't seem to hurt performance and provides an additional safety measure if there are additional instabilities. The real fix will be to make progress on #94188 and use a collection type that doesn't leak iteration order into fingerprints. |
📌 Commit 9421219 has been approved by |
…oerister Return a FxIndexSet in is_late_bound query. This return value is iterated upon by borrowck, hence the need to preserve a deterministic iteration order. Fixes rust-lang#98890 Affects rust-lang#96655 I don't know if this supersedes rust-lang#98924 or fixes an unrelated bug. r? `@michaelwoerister` This may deserve a backport.
⌛ Testing commit 9421219 with merge 049ee8c62795b3ea3b662f89efc209ddbd78d5ec... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
⌛ Testing commit 9421219 with merge e55a669443e142e23a46f3d12eae0c0dd7e9082f... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Based on the latest tests failures. I'll switch to waiting on author, if it's ok. Feel free to request a review with @rustbot author |
I'm closing this. #98959 has fixed the root cause and the work that will eventually come out of rust-lang/compiler-team#533 will provide nicer "hardening" than what's implemented in this PR. |
This potentially fixes issue #96655, but I was not able to actually reproduce it.
r? @Aaron1011