-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Stable 1.1 ICE: assertion failed: bound_list_is_sorted(&bounds.projection_bounds) #27222
Comments
It seems like I can make the ICE go away by replacing a member variable
with one that uses an equivalent trait which doesn't use associated types:
Swapping that in removes the ICE, swapping it out brings the ICE back. So, maybe something isn't working great for boxed traits with associated types. The commit that fixes things is frankmcsherry/timely-dataflow@fcb32c5...68ca8e9 |
Doing some testing, and the repro in #25467 (not mine) is way simpler. It also explodes on 1.1 stable, with a similar complaint. Just boxing a trait with two associated types. |
I run into this problem, too (with stable |
The sort key is a (DefId, Name), which is *not* stable between runs, so we must re-sort when loading. Fixes rust-lang#24063 Fixes rust-lang#25467 Fixes rust-lang#27222 Fixes rust-lang#28377
It looks like if you go and grab this commit of timely-dataflow from github, you get a nicely reproducible ICE. TravisCI gets it too! In case anything changes in the meantime, the commit you want is
frankmcsherry/timely-dataflow@fcb32c5
Related issues: #24063 #25467. The times I've seen this before I haven't be able to reproduce it, but since it seems to happen from a clean pull, I thought I would show you.
To repro, just follow the commands here. git clone, cargo build, cargo test. Boom!
The text was updated successfully, but these errors were encountered: