-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[MONO][Interp] Tracking runtime test failures with Mono interpreter #54383
Comments
Tagging subscribers to this area: @BrzVlad Issue DetailsComparing to Android x64 with JIT, here are the additional 93 tests failing to run on Android x64 with interpreter
|
The title is misleading since these issues have nothing to do with android. These tests were already disabled on our CI runs on interpreter, however they were not triaged in detail. When it comes to android, it would have been more interesting to see whether there are any additional issues compared to desktop interpreter, which normally shouldn't be. |
I see. Let me clean the issues up. |
These are existing issues since .NET 5. None of them is currently block our customer. We will revisit them in .NET 7. |
I went through and reorganized the list into 4 lists. The first group "Probably worth investigating in NET6" are tests that I think a quick investigation will reprioritize for .NET 7. I suspect most of these are failing because the test is some bad IL, and the interpreter is generally not designed to gracefully exit for patently broken code. The second group "Also warrants a deeper investigation in .NET6" Seem like they might be real high-impact issues. The third group "Other issues" - particularly the JIT ones - I can't really tell from looking at them how big the impact is. I don't think they're intentionally bad IL, but I also can't tell from a superficial scanning of them if they're trying unlikely edge cases or something that is likely to be common The fourth group are all the cases where the IL is intentionally bad and we're unlikely to see this from normal C# code. |
Moving to 8.0.0 |
Here are the issues:
Probably worth investigating in NET6 - most of these are probably intentionally bad IL or other IL edge case behavior (and could be triaged to lower priority pretty quickly) - but they might uncover interpreter issues:
Also warrants a deeper investigation in .NET6 - the failures here are not well understood:
Other issues:
Lower priority:
The text was updated successfully, but these errors were encountered: