-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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: Interop/IJW/CopyConstructorMarshaler/CopyConstructorMarshaler/CopyConstructorMarshaler.cmd #100751
Comments
@jkoritzinsky Could this be related to #100050? |
Yes, it looks like in this JIT Stress mode, the codegen is introducing additional copies/spills into the IL stub. This isn't a failure due to changes in that PR, but a bug (at least for that scenario) exposed by the test improvements. |
Failed in: runtime-coreclr jitstress-random 20240421.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstress-random 20240517.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstress-random 20240729.1 Failed tests:
Error message:
Stack trace:
|
I finally had a chance to look at this. I'm still investigating exactly what is causing the failure, but I've finally narrowed it down to exactly which function and stress modes. The failure is due to the combination of |
I've isolated the problem into a non-stress scenario. When a struct is attributed with |
This issue should still be closed as there is a fix in 9.0 |
Hi @jkoritzinsky, we're still hitting this failure in |
It looks like it's a different JitStress failure (JitStress 2) so we can use the other issue that was opened to track it. |
Failed in: runtime-coreclr jitstress-random 20240407.1
Failed tests:
Error message:
Stack trace:
The text was updated successfully, but these errors were encountered: