-
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: JIT/Directed/tls/TestTLSWithLoadedDlls/TestTLSWithLoadedDlls.cmd #113816
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
I tried to repro this on local macos arm64 box, and it doesn't repro for me. Looking at the logs, looks like the crash dump was created right after the test execution started so I spent some time looking at the dump and nothing suspicious occurs to me on any of the threads. @davidwrighton in case you have any clue? backtrace of all threads
|
Also, previously it also showed up in outerloop in #113725 and I thought it is intermittent failure while copying several files (that the test exercises). In that, it didn't need any special JITStress flags, so this seems to be crashing (at least from the logs) without any flags. Locally, I tried increasing the number of shared libraries we load, increase the time we iterate in the |
Since this is very inconsistent and shown up twice so far in 2 different pipelines, I am removing the label of "blocking" from it. |
Failed in: runtime-coreclr jitstress-random 20250323.1
Failed tests:
Error message:
Stack trace:
The text was updated successfully, but these errors were encountered: