crypto/x509: TestPlatformVerifierLegacy/self-signed_leaf failures

[gopherbot]

#!watchflakes
default <- pkg == "crypto/x509" && test == "TestPlatformVerifierLegacy/self-signed_leaf"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestPlatformVerifierLegacy/self-signed_leaf
    root_windows_test.go:102: tls connection failed: read tcp 10.138.0.106:52753->104.154.89.105:443: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
--- FAIL: TestPlatformVerifierLegacy/self-signed_leaf (19.29s)

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "crypto/x509" && test == "TestPlatformVerifierLegacy/self-signed_leaf"

2024-05-06 21:02 go1.22-windows-amd64-longtest release-branch.go1.22@947e43e3 crypto/x509.TestPlatformVerifierLegacy/self-signed_leaf (log)

=== RUN   TestPlatformVerifierLegacy/self-signed_leaf
    root_windows_test.go:102: tls connection failed: read tcp 10.138.0.106:52753->104.154.89.105:443: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
--- FAIL: TestPlatformVerifierLegacy/self-signed_leaf (19.29s)

2024-05-13 21:10 go1.22-windows-amd64-longtest release-branch.go1.22@d4a81ec7 crypto/x509.TestPlatformVerifierLegacy/self-signed_leaf (log)

=== RUN   TestPlatformVerifierLegacy/self-signed_leaf
    root_windows_test.go:102: tls connection failed: dial tcp 104.154.89.105:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
--- FAIL: TestPlatformVerifierLegacy/self-signed_leaf (21.06s)

— watchflakes