-
Notifications
You must be signed in to change notification settings - Fork 7
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
main-eisop crash in TernaryUnspecVsNoQualifier #159
Comments
Thanks for the report! The smallest I could make the test case is:
Without the Do you know why this crash doesn't show up in CI? The report only mentions this file with an |
Hmm, I don't remember what it does with crashes.... |
04b8d84, together with the other changes in #165, fixes this issue. When using |
Fixed by #165. |
This crash is back (as is #160) as of "Re-instate work-around to type variable bound issue." (I hadn't retested #165 after that commit, so I didn't notice until I went to test #171.) Your test case above reproduces the failure in main-eisop (at 76b33c9), so I imagine you may have already encountered this as you work to get the tests in the |
Fixed by #174. |
After building the checker (using the JSpecify JDK that uses the old JSpecify package, for the record, as in #156, but I doubt that's relevant), I cloned
jspecify
as a sibling directory and switched to thesamples-google-prototype
branch. Then:I don't immediately see this crash among my results from running the checker on Google's codebase yester (though it's possible that that's only because we were prevented from getting that far by other errors :)). But I see reference to "root needs to be set when used on trees" in the commits referenced from jspecify/checker-framework#11 (also discussed in jspecify/checker-framework#45).
Given that those posts discuss stub files, and given that I hadn't seen the problem inside Google yet, I'd hoped that the problem would go away if I passed
-Aignorejdkastub
. But I'm seeing it even with that flag.I do notice
inheritOverriddenDeclAnnos
in the stack trace, so this seems like more reason to provide a way to skip the inheriting of annotations, as discussed in jspecify/checker-framework#11. Indeed, the error goes away if I make a change similar to jspecify/checker-framework@f3e9f21. (I don't know if the full set of changes is necessary.)The text was updated successfully, but these errors were encountered: