-
Notifications
You must be signed in to change notification settings - Fork 4.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
Test failure Loader/classloader/explicitlayout/NestedStructs/case05/case05.sh #62311
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
It's the LLVM AOT lane. which makes sense - we may have only loaded some AOT image info about the nested class, not necessarilly fully initialized it. /cc @simonrozsival |
@vargaz @thaystg the new test from #60770 is failing on the AOT lane - looks like Look at
|
On AOT the field's class may not have been fully inited yet. Related to dotnet#62311
@steveisok Another pair of failures that would have been caught if we ran the linux runtime test lanes on PRs |
When the test case05 is moved to a console app, the following happens. A method tries to instantiate a type with an invalid layout, its @lambdageek What is the expected behavior here? Should the AOT compiler replace the |
In general, we have been moving in the direction of following NativeAOT's behavior, which is to not fail the AOT compilation, but to generate code that throws something at runtime. I'm not sure if that is what they do for this specific test, too. |
The said tests have been reenabled in #91261 and seem to work fine. Closing the issue. |
Edit there are two separate issues here all on the Linux x64 LLVM AOT lane:
Run: runtime 20211202.64
Failed test:
Error message:
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: