Repository navigation
Description
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1639090
Build error leg or test failing: linux-x64 / linux_musl-x64 Release CoreCLR_AllSubsets - System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_ServerCertificates_Test.UseCallback_BadCertificate_ExpectedPolicyErrors
Error Details
Three cases of UseCallback_BadCertificate_ExpectedPolicyErrors fail on the linux-x64 (Ubuntu 26.04) and linux_musl-x64 (Alpine 3.24) CoreCLR_AllSubsets legs in every scheduled runtime build of main from 1634000 (109674e8cdc) through 1639090. These cases were added by #135618 (f5216009644, first in build 1634000), which moved the tests from badssl.com to loopback servers; before it the method was outer-loop only.
The Android failures of these tests are tracked in #135988; its error message list doesn't match the logs of the two CoreCLR_AllSubsets legs, whose xunit output puts [FAIL] at the end of the line.
On the CI of #135975 (the Android fix; Debug legs), the expired and wrong-host cases pass on both Linux legs; the self-signed case (expired: False, wrongHostName: False) still fails there with UntrustedRoot | InvalidBasicConstraints.
System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_ServerCertificates_Test.UseCallback_BadCertificate_ExpectedPolicyErrors(expired: True, wrongHostName: False, expectedErrors: RemoteCertificateChainErrors) [FAIL]
System.AggregateException : One or more errors occurred. (The SSL connection could not be established, see inner exception.) (Authentication failed, see inner exception.)
---- System.Net.Http.HttpRequestException : The SSL connection could not be established, see inner exception.
-------- System.Security.Authentication.AuthenticationException : Authentication failed, see inner exception.
------------ Assert.Equal() Failure: Values differ
Expected: NotTimeValid
Actual: NotTimeValid | InvalidBasicConstraints
---- System.Security.Authentication.AuthenticationException : Authentication failed, see inner exception.
-------- Interop+OpenSsl+SslException : SSL Handshake failed with OpenSSL error - SSL_ERROR_SSL.
------------ Interop+Crypto+OpenSslCryptographicException : error:0A000438:SSL routines::tlsv1 alert internal error
System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_ServerCertificates_Test.UseCallback_BadCertificate_ExpectedPolicyErrors(expired: False, wrongHostName: False, expectedErrors: RemoteCertificateChainErrors) [FAIL]
...
------------ Assert.Equal() Failure: Values differ
Expected: UntrustedRoot
Actual: UntrustedRoot | InvalidBasicConstraints
System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_ServerCertificates_Test.UseCallback_BadCertificate_ExpectedPolicyErrors(expired: False, wrongHostName: True, expectedErrors: RemoteCertificateNameMismatch) [FAIL]
...
------------ Assert.Equal() Failure: Values differ
Expected: RemoteCertificateNameMismatch
Actual: RemoteCertificateNameMismatch | RemoteCertificateChainErrors
Error Message
{
"ErrorMessage": "",
"ErrorPattern": "Actual:\\s+(NotTimeValid|UntrustedRoot|RemoteCertificateNameMismatch) \\| (InvalidBasicConstraints|RemoteCertificateChainErrors)",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Note
AI-generated, written at my direction and reviewed by me before posting. Leg results and failure text are from the Helix console logs of builds 1633173 through 1639090, PR build 1639105 and the CI of #135975; the pattern was matched case-insensitively with .NET Regex against those logs: three hits per failing Linux log on main, one per Linux log on #135975's CI, none in the Android logs of builds 1639090 and 1639105 or in build 1633173.
Activity
dotnet-policy-service commentedon Oct 17, 2026
Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.
caraioniurie47 commentedon Oct 17, 2026
Could someone add the
Known Build Error,blocking-clean-ciandarea-System.Net.Httplabels so Build Analysis picks this up? Thanks.MihaZupan commentedon Oct 17, 2026
I think this was also fixed by #135975