-
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
Authentication_EmptyCredentials_Fails [FAIL] #112312
Comments
I think the fundamental question is if the machines in the Helix pool changed configuration. We have seen this before on some machines that had NTLM disabled through registry settings. Unfortunately we never quite pinpointed the exact settings that caused it (or at least I don't remember it). |
Tagging subscribers to this area: @dotnet/ncl |
I think there was Windows update and it is now similar to the Server 2025. |
Is #112370 a duplicate of this issue? |
yes. Breaking branch that did not change is string indication of image change. |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=941931
Build error leg or test failing: System.Net.Security.Tests.NegotiateStreamStreamToStreamTest_Async_Array.NegotiateStream_StreamToStream_Authentication_EmptyCredentials_Fails
Pull request: #112188
Error Message
Fill the error message using step by step known issues guidance.
Output:
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=941931
Error message validated:
[_Authentication_EmptyCredentials_Fails [FAIL]
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/9/2025 1:48:10 AM UTC
Report
Summary
Report
Summary
The text was updated successfully, but these errors were encountered: