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

gopherbot · 2022-11-17T16:05:26Z

#!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

The text was updated successfully, but these errors were encountered:

gopherbot · 2022-11-17T16:07:21Z

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 · 2022-11-17T18:38:50Z

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

gopherbot · 2022-11-21T17:14:30Z

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 · 2022-11-21T17:28:08Z

I think this is probably related to #55050.

sahnnu · 2023-06-23T18:38:50Z

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

gopherbot · 2023-08-18T23:17:59Z

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 · 2023-10-09T23:09:59Z

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 · 2023-10-09T23:30:45Z

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 · 2023-10-10T06:25:04Z

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

gopherbot · 2023-10-10T17:28:50Z

Found new dashboard test flakes for:

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

2023-10-10 16:10 windows-amd64-longtest go@24ae2d92 crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (34.44s)
    --- FAIL: TestPlatformVerifierLegacy/untrusted_root (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 · 2023-10-10T18:31:06Z

Found new dashboard test flakes for:

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

2023-10-10 16:50 windows-amd64-longtest go@1493dd3c crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (28.05s)
    --- FAIL: TestPlatformVerifierLegacy/untrusted_root (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.

— watchflakes

gopherbot · 2023-10-10T20:35:33Z

Found new dashboard test flakes for:

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

2023-10-10 16:18 windows-amd64-longtest go@e175f27f crypto/x509.TestPlatformVerifier (log)

--- FAIL: TestPlatformVerifier (28.24s)
    --- FAIL: TestPlatformVerifier/untrusted_root (21.03s)
        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.

2023-10-10 16:26 windows-amd64-longtest go@8042fd87 crypto/x509.TestPlatformVerifier (log)

--- FAIL: TestPlatformVerifier (43.69s)
    --- 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

gopherbot · 2023-10-25T15:04:48Z

Found new dashboard test flakes for:

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

2023-10-10 18:10 windows-amd64-longtest go@9465990e crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (21.78s)
    --- FAIL: TestPlatformVerifierLegacy/wrong_host_for_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.

— watchflakes

gopherbot · 2023-12-11T22:27:50Z

Change https://go.dev/cl/548976 mentions this issue: crypto/x509: remove TestPlatformVerifierLegacy tests

gopherbot · 2023-12-11T22:43:15Z

Found new dashboard test flakes for:

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

2023-12-11 21:37 windows-amd64-longtest go@c22781cb crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (21.84s)
    --- FAIL: TestPlatformVerifierLegacy/expired_leaf (5.82s)
        root_windows_test.go:102: tls connection failed: EOF

— watchflakes

gopherbot · 2024-02-06T22:50:18Z

Found new dashboard test flakes for:

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

2023-12-15 18:08 windows-amd64-longtest go@796f59df crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (34.09s)
    --- FAIL: TestPlatformVerifierLegacy/untrusted_root (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 · 2024-02-18T00:35:24Z

Found new dashboard test flakes for:

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

2024-02-17 06:03 windows-amd64-longtest go@86a32d6d crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (63.02s)
    --- FAIL: TestPlatformVerifierLegacy/expired_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.
    --- FAIL: TestPlatformVerifierLegacy/untrusted_root (21.04s)
        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 · 2024-02-20T15:59:26Z

Found new dashboard test flakes for:

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

2024-02-20 06:04 windows-amd64-longtest go@d42cd452 crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (24.93s)
    --- 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

rolandshoemaker · 2024-02-20T18:50:23Z

Closed the wrong issue 🤦, should have been #65626.

rolandshoemaker · 2024-02-20T18:50:51Z

Oh wait, no, this is also Legacy.

gopherbot · 2024-02-20T20:10:03Z

Found new dashboard test flakes for:

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

2024-02-20 06:04 gotip-windows-amd64-longtest go@d42cd452 crypto/x509.TestPlatformVerifierLegacy/expired_leaf (log)

=== RUN   TestPlatformVerifierLegacy/expired_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/expired_leaf (21.51s)

2024-02-20 06:04 gotip-windows-amd64-longtest go@d42cd452 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.38s)

— watchflakes

gopherbot · 2024-05-07T16:49:36Z

Found new dashboard test flakes for:

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

2024-05-06 21:02 windows-amd64-longtest go@947e43e3 crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (55.60s)
    --- FAIL: TestPlatformVerifierLegacy/untrusted_root (21.00s)
        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.

2024-05-06 21:03 windows-amd64-longtest go@78d89b2b crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (85.23s)
    --- FAIL: TestPlatformVerifierLegacy/expired_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.
    --- FAIL: TestPlatformVerifierLegacy/self-signed_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 · 2024-05-08T11:04:10Z

Found new dashboard test flakes for:

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

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-06 21:02 go1.22-windows-amd64-longtest release-branch.go1.22@947e43e3 crypto/x509.TestPlatformVerifierLegacy/wrong_host_for_leaf (log)

=== RUN   TestPlatformVerifierLegacy/wrong_host_for_leaf
    root_windows_test.go:102: tls connection failed: tls: first record does not look like a TLS handshake
--- FAIL: TestPlatformVerifierLegacy/wrong_host_for_leaf (15.52s)

2024-05-06 21:03 go1.21-windows-amd64-longtest release-branch.go1.21@78d89b2b crypto/x509.TestPlatformVerifierLegacy/wrong_host_for_leaf (log)

=== RUN   TestPlatformVerifierLegacy/wrong_host_for_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/wrong_host_for_leaf (21.35s)

— watchflakes

gopherbot · 2024-05-14T00:18:06Z

Found new dashboard test flakes for:

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

2024-05-13 21:10 windows-amd64-longtest go@d4a81ec7 crypto/x509.TestPlatformVerifierLegacy (log)

--- FAIL: TestPlatformVerifierLegacy (64.18s)
    --- FAIL: TestPlatformVerifierLegacy/expired_leaf (18.70s)
        root_windows_test.go:102: tls connection failed: tls: first record does not look like a TLS handshake
    --- FAIL: TestPlatformVerifierLegacy/wrong_host_for_leaf (21.04s)
        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.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.

— watchflakes

gopherbot · 2024-05-14T00:47:24Z

Found new dashboard test flakes for:

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

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

=== RUN   TestPlatformVerifierLegacy/expired_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/expired_leaf (21.20s)

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)

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

=== RUN   TestPlatformVerifierLegacy/wrong_host_for_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/wrong_host_for_leaf (21.06s)

— watchflakes

rolandshoemaker · 2024-05-14T02:23:01Z

@gopherbot please open backport issues for this. It's an incredibly noisy test which is currently only failing on the release branches. Those branches currently have the better tests enabled, so we should just backport https://go.dev/cl/548976 and remove these old broken ones to make the builders happy.

gopherbot · 2024-05-14T02:23:32Z

Backport issue(s) opened: #67351 (for 1.21), #67352 (for 1.22).

Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases.

gopherbot · 2024-05-16T02:27:25Z

Found new dashboard test flakes for:

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

2024-05-13 21:10 go1.21-windows-amd64-longtest release-branch.go1.21@0fa334d4 crypto/x509.TestPlatformVerifierLegacy/wrong_host_for_leaf (log)

=== RUN   TestPlatformVerifierLegacy/wrong_host_for_leaf
    root_windows_test.go:102: tls connection failed: tls: first record does not look like a TLS handshake
--- FAIL: TestPlatformVerifierLegacy/wrong_host_for_leaf (61.34s)

— watchflakes

gopherbot · 2024-05-16T19:57:29Z

Change https://go.dev/cl/586215 mentions this issue: [release-branch.go1.21] crypto/x509: remove TestPlatformVerifierLegacy tests

gopherbot · 2024-05-16T19:57:59Z

Change https://go.dev/cl/586235 mentions this issue: [release-branch.go1.22] crypto/x509: remove TestPlatformVerifierLegacy tests

…y tests They are no longer necessary, woohoo! Updates #52108 Fixes #56791 Fixes #67351 Change-Id: I11a4c17162da4295309f74f2f8362bab0f506f78 Reviewed-on: https://go-review.googlesource.com/c/go/+/548976 Run-TryBot: Roland Shoemaker <roland@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Roland Shoemaker <roland@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> (cherry picked from commit c1828fb) Reviewed-on: https://go-review.googlesource.com/c/go/+/586215 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@google.com>

…y tests They are no longer necessary, woohoo! Updates #52108 Fixes #56791 Fixes #67352 Change-Id: I11a4c17162da4295309f74f2f8362bab0f506f78 Reviewed-on: https://go-review.googlesource.com/c/go/+/548976 Run-TryBot: Roland Shoemaker <roland@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Roland Shoemaker <roland@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> (cherry picked from commit c1828fb) Reviewed-on: https://go-review.googlesource.com/c/go/+/586235 Auto-Submit: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>

rolandshoemaker · 2024-05-17T01:41:51Z

Going to close this under the assumption that we should no longer see these failures.

gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Nov 17, 2022

bcmills changed the title ~~crypto/x509: TestPlatformVerifier failures~~ crypto/x509: TestPlatformVerifier failures on Windows due to broken connections Nov 17, 2022

bcmills added the OS-Windows label Nov 17, 2022

bcmills added this to the Backlog milestone Nov 17, 2022

bcmills added the Security label Jun 23, 2023

bcmills mentioned this issue Dec 11, 2023

crypto/x509: come up with better solution for testing platform verifiers #52108

Open

gopherbot closed this as completed in c1828fb Feb 20, 2024

rolandshoemaker reopened this Feb 20, 2024

rolandshoemaker closed this as completed Feb 20, 2024

gopherbot reopened this May 7, 2024

This was referenced May 14, 2024

crypto/x509: TestPlatformVerifier failures on Windows due to broken connections [1.21 backport] #67351

Closed

crypto/x509: TestPlatformVerifier failures on Windows due to broken connections [1.22 backport] #67352

Closed

rolandshoemaker closed this as completed May 17, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

gopherbot commented Nov 17, 2022 •

edited by bcmills

Loading

gopherbot commented Nov 17, 2022

bcmills commented Nov 17, 2022

gopherbot commented Nov 21, 2022

rolandshoemaker commented Nov 21, 2022

sahnnu commented Jun 23, 2023

gopherbot commented Aug 18, 2023

gopherbot commented Oct 9, 2023

gopherbot commented Oct 9, 2023

gopherbot commented Oct 10, 2023

gopherbot commented Oct 10, 2023

gopherbot commented Oct 10, 2023

gopherbot commented Oct 10, 2023

gopherbot commented Oct 25, 2023

gopherbot commented Dec 11, 2023

gopherbot commented Dec 11, 2023

gopherbot commented Feb 6, 2024

gopherbot commented Feb 18, 2024

gopherbot commented Feb 20, 2024

rolandshoemaker commented Feb 20, 2024

rolandshoemaker commented Feb 20, 2024

gopherbot commented Feb 20, 2024

gopherbot commented May 7, 2024

gopherbot commented May 8, 2024

gopherbot commented May 14, 2024

gopherbot commented May 14, 2024

rolandshoemaker commented May 14, 2024

gopherbot commented May 14, 2024

gopherbot commented May 16, 2024

gopherbot commented May 16, 2024

gopherbot commented May 16, 2024

rolandshoemaker commented May 17, 2024

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

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

Comments

gopherbot commented Nov 17, 2022 • edited by bcmills Loading

gopherbot commented Nov 17, 2022

bcmills commented Nov 17, 2022

gopherbot commented Nov 21, 2022

rolandshoemaker commented Nov 21, 2022

sahnnu commented Jun 23, 2023

gopherbot commented Aug 18, 2023

gopherbot commented Oct 9, 2023

gopherbot commented Oct 9, 2023

gopherbot commented Oct 10, 2023

gopherbot commented Oct 10, 2023

gopherbot commented Oct 10, 2023

gopherbot commented Oct 10, 2023

gopherbot commented Oct 25, 2023

gopherbot commented Dec 11, 2023

gopherbot commented Dec 11, 2023

gopherbot commented Feb 6, 2024

gopherbot commented Feb 18, 2024

gopherbot commented Feb 20, 2024

rolandshoemaker commented Feb 20, 2024

rolandshoemaker commented Feb 20, 2024

gopherbot commented Feb 20, 2024

gopherbot commented May 7, 2024

gopherbot commented May 8, 2024

gopherbot commented May 14, 2024

gopherbot commented May 14, 2024

rolandshoemaker commented May 14, 2024

gopherbot commented May 14, 2024

gopherbot commented May 16, 2024

gopherbot commented May 16, 2024

gopherbot commented May 16, 2024

rolandshoemaker commented May 17, 2024

gopherbot commented Nov 17, 2022 •

edited by bcmills

Loading