-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Test failure Loader\\classloader\\Casting\\Functionpointer\\Functionpointer.cmd #81106
Comments
@mangod9, PTAL. It is blocking outerloop for many tests. |
@trylek is there any recent change which would cause these failures? |
I'm not aware of any particular recent suspicious change, however the function pointers are a relatively new feature that continues to proliferate through the framework; this type of error can be randomly triggered by adding some new code to SPC or other assembly i.o.w. by ambient growth of the code base. I have reassigned the bug to myself, I'm going to prioritize investigating it, this type of bug is usually relatively easy to track down and fix, the problem is just that there's some aspect of the function pointer type (e.g. calling convention or other flags) that is not serialized into the internal node name. |
For the recent change that would cause these failures, I guess it's this one: |
@fanyang-mono, your PR is causing failures that is affecting many of outerloop runs. Please take a look with a high priority.
|
@JulieLeeMSFT - I believe this is a new test added as part of @fanyang-mono PR -- should we disable those for CoreCLR to get the outerloop unblocked ? |
@JulieLeeMSFT According to the error message, it seems to me that CoreCLR is not handling the testing scenarios that I added in my PR properly. As Sam mentioned earlier, we could disable the newly added test to make the CI lane passes. But further investigation on CoreCLR side is needed. Also, what does |
@fanyang-mono and @SamMonoRT, I see that @trylek has a fix. Thanks all. |
@trylek @JulieLeeMSFT -- Please note, the original PR which added this test was also approved for backport to 7.0 via #80927 --- I'm not certain if your fix needs to be backported (or added to original backport PR) ? |
@SamMonoRT - well, if the test gets backported to 7.0, it will certainly start to fail in Crossgen2 builds because of this bug. For now I assume this means that the Crossgen2 fix also needs to request backport to 7.0, please let me know if you think otherwise. |
@fanyang-mono - for |
Yes, we should backport your fix to 7.0. The merging window is closed at the moment. I'll add a note to that PR, so Carlos is aware and can merge both of them together. |
This fixes the recently introduced issue dotnet#81106 tracking Crossgen2 crash due to not being able to distinguish two function pointers differing only by calling convention (one of the pointers is Static and the other is Static | UnmanagedCallingConvention). Thanks Tomas
…81122) This fixes the recently introduced issue #81106 tracking Crossgen2 crash due to not being able to distinguish two function pointers differing only by calling convention (one of the pointers is Static and the other is Static | UnmanagedCallingConvention). This change also removes the issues.targets exclusion for the new function pointer test that Fan Yang had to add to unblock merging in the test in the first place. Thanks Tomas * Delete superfluous comment per Michal's PR feedback
Failed in Run: runtime-coreclr outerloop 20230124.1 and many ohter outerloop runs
Failed tests:
Error message:
Stack trace:
The text was updated successfully, but these errors were encountered: