-
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: Interop/PInvoke/CriticalHandles/Test/Test/Test.cmd #103939
Comments
Failed in: runtime-coreclr gcstress0x3-gcstress0xc 20240714.1 Failed tests:
Error message:
Stack trace:
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
@AndyAyersMS, PTAL. |
Also failed in runtime-coreclr gcstress0x3-gcstress0xc/20240714.1
Stack trace:
|
I was able to repro this on windows x64, but it took 506 runs... doesn't feel like a codegen issue, but will keep looking. |
Yes, it could be. This test has a bunch of scenarios that rely on deterministic GC.Collect();
GC.WaitForPendingFinalizers() |
I saw your comment, but was waiting for my fix to go in and just suggest to wait for more failures, if they happen. It is easy to rely on determinism of It may take some more time for my fix to go in though. Hopefully less than an hour. I am waiting for GC stress to finish. |
#105289 has been merged. Hopefully this issue will be fixed with that. |
No failures over the weekend, so closing this. |
Failed in: runtime-coreclr r2r-extra 20240623.1
Failed tests:
Error message:
Stack trace:
The text was updated successfully, but these errors were encountered: