-
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 baseservices/threading/regressions/2164/foreground-shutdown/foreground-shutdown.cmd #83658
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. |
Tagging subscribers to this area: @mangod9 Issue DetailsFailed in Run: runtime-coreclr outerloop 20230318.3 Failed tests:
Error message:
Stack trace:
|
Failed again in: runtime-coreclr r2r-extra 20230326.1 Failed test:
Error message:
|
fyi - This test was switched to running in a merged test group around the time of this failure. However, it sets |
Is this an intermittent failure? @kouvel if he has any insights into this test. |
Failed again in: runtime-coreclr jitstress 20230402.1 Failed test:
Error message:
|
Probably dup of #84006 |
Failed again in: runtime-coreclr outerloop 20230417.2 Failed test:
Error message:
|
Failed again in: runtime-coreclr jitstress 20230425.5 Failed test:
Error message:
|
yeah probably needs to be disabled. @eduardo-vp since you are running threading/TP tests recently, could you please take a look at this? |
This test has failed across many configurations, but apparently only on Windows. Tracked by dotnet#84006, dotnet#83658.
Failed again in: runtime-coreclr jitstress 20230507.2 Failed tests:
Error message:
Stack trace:
|
Failed again in: runtime-coreclr jitstress-isas-x86 20230610.1 Failed tests:
�Error message:
�Stack trace:
|
Failed again in: runtime-coreclr jitstressregs-x86 20230702.1 Failed tests:
Error message:
Stack trace:
|
Failed again in: runtime-coreclr jitstress2-jitstressregs 20230722.1 Failed tests:
Error message:
Stack trace:
|
Failed again in: runtime-coreclr r2r-extra 20230814.1 Failed tests:
Error message:
Stack trace:
|
Failed again in: runtime-coreclr pgostress 20230825.1 Failed tests:
Error message:
Stack trace:
|
It's not clear yet why this is happening. This issue seems to be different from #84006, which is a hang and I have a fix for. For this issue I've only seen it occur one time locally in many hours of running the tests. It'll probably need more testing with additional logging in the runtime to get more info when it does happen. For now, I've moved this issue to 9.0 and I'll disable the test. |
…pending on timing with GCs - On Windows when a thread calls `ExitProcess`, the `TlsDestructionMonitor` for the thread appears to be destructed after all other threads in the process are torn down. It's possible for a GC to be in progress during that time, and the thread cleanup code in `TlsDestructionMonitor` tries to enter cooperative GC mode to fix the frame pointer, leading to a hang. Fixed by deactivating the `TlsDestructionMonitor` for the thread before calling `ExitProcess`. - Also disabled the relevant test due to a different issue dotnet#83658 occurring in the same test on multiple platforms/architectures that is not understood yet. Fixes dotnet#84006
Issue dotnet#83658 appears to be occurring on multiple platforms/architectures and is not understood yet.
Issue #83658 appears to be occurring on multiple platforms/architectures and is not understood yet.
Failed in Run: runtime-coreclr outerloop 20230318.3
Failed tests:
Error message:
Stack trace:
The text was updated successfully, but these errors were encountered: