-
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
InvalidKeySize_DoesNotInvalidateKey: An internal consistency check failed. #111350
Comments
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones |
Failed in: runtime-coreclr libraries-jitstress-random 20250113.1 Failed tests:
Error message:
Stack trace:
|
Assigned to @bartonjs for triage |
Different callstack, but it's the same "Windows CNG is in a bad state", and we've not been successful in getting their help to investigate. |
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=915376&view=ms.vss-test-web.build-test-results-tab&runId=24176138&resultId=113288&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab
(net10.0-windows-Release-arm64-jitstress_random_2-Windows.11.Arm64.Open on runtime-coreclr libraries-jitstress-random)
I couldn't use "Known build fauilure" template because https://helix.dot.net/BuildAnalysis/CreateKnownIssues is down.
The text was updated successfully, but these errors were encountered: