crypto/x509: TestPlatformVerifier failures on Windows due to broken connections

[gopherbot]

#!watchflakes
post <- goos == "windows" && pkg == "crypto/x509" && test ~ `^TestPlatformVerifier`

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestPlatformVerifier (41.53s)
    --- FAIL: TestPlatformVerifier/self-signed_leaf (5.03s)
        root_windows_test.go:90: tls connection failed: EOF
    --- FAIL: TestPlatformVerifier/untrusted_root (24.13s)
        root_windows_test.go:90: tls connection failed: tls: first record does not look like a TLS handshake

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "crypto/x509" && test == "TestPlatformVerifier"

2022-11-09 03:01 windows-amd64-longtest go@b4591662 crypto/x509.TestPlatformVerifier (log)

--- FAIL: TestPlatformVerifier (41.53s)
    --- FAIL: TestPlatformVerifier/self-signed_leaf (5.03s)
        root_windows_test.go:90: tls connection failed: EOF
    --- FAIL: TestPlatformVerifier/untrusted_root (24.13s)
        root_windows_test.go:90: tls connection failed: tls: first record does not look like a TLS handshake

2022-11-15 16:24 windows-amd64-longtest go@6df54215 crypto/x509.TestPlatformVerifier (log)

--- FAIL: TestPlatformVerifier (45.34s)
    --- FAIL: TestPlatformVerifier/expired_leaf (21.01s)
        root_windows_test.go:90: 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: TestPlatformVerifier/wrong_host_for_leaf (21.01s)
        root_windows_test.go:90: 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.

— watchflakes

[bcmills]

(attn @golang/windows, @rolandshoemaker; compare #52108)

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "crypto/x509" && test == "TestPlatformVerifier"

2022-11-18 23:57 windows-amd64-longtest go@4f0d3bcd crypto/x509.TestPlatformVerifier (log)

--- FAIL: TestPlatformVerifier (24.72s)
    --- FAIL: TestPlatformVerifier/expired_leaf (21.01s)
        root_windows_test.go:90: 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.

— watchflakes

[rolandshoemaker]

I think this is probably related to #55050.

[sahnnu]

HOw to handle this issue . Currently i am facing this with go 1.20 on windows 10

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "crypto/x509" && test ~ `^TestPlatformVerifier`

2023-08-18 17:06 darwin-amd64-longtest go@795e7796 crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (76.37s)
    root_darwin_test.go:103: tls connection failed: dial tcp 142.250.191.238:443: connect: operation timed out
    --- FAIL: TestPlatformVerifierLegacy/expired_leaf_(custom_time) (75.01s)
        testing.go:1490: test executed panic(nil) or runtime.Goexit: subtest may have called FailNow on a parent test

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "crypto/x509" && test ~ `^TestPlatformVerifier`

2023-10-09 21:56 windows-amd64-longtest go@5955a03e crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (29.31s)
    --- FAIL: TestPlatformVerifierLegacy/expired_leaf (21.01s)
        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.

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "crypto/x509" && test ~ `^TestPlatformVerifier`

2023-10-09 22:05 windows-amd64-longtest go@8f61fab6 crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (31.67s)
    --- FAIL: TestPlatformVerifierLegacy/self-signed_leaf (21.02s)
        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.

2023-10-09 22:06 windows-amd64-longtest go@51bdd3bd crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (22.28s)
    --- FAIL: TestPlatformVerifierLegacy/expired_leaf (21.03s)
        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.

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "crypto/x509" && test ~ `^TestPlatformVerifier`

2023-10-09 18:53 darwin-amd64-longtest go@a8ca649b crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (80.15s)
    root_darwin_test.go:103: tls connection failed: dial tcp 104.154.89.105:443: connect: operation timed out
    --- FAIL: TestPlatformVerifierLegacy/self-signed_leaf (75.06s)
        testing.go:1488: test executed panic(nil) or runtime.Goexit: subtest may have called FailNow on a parent test

— watchflakes