Skip to content
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

crypto/x509: TestPlatformVerifierLegacy/wrong_host_for_leaf failures #67993

Open
gopherbot opened this issue Jun 14, 2024 · 2 comments
Open

crypto/x509: TestPlatformVerifierLegacy/wrong_host_for_leaf failures #67993

gopherbot opened this issue Jun 14, 2024 · 2 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.

Comments

@gopherbot
Copy link
Contributor

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

Issue created automatically to collect these failures.

Example (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 gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jun 14, 2024
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "crypto/x509" && test == "TestPlatformVerifierLegacy/wrong_host_for_leaf"
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)
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)
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
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "crypto/x509" && test == "TestPlatformVerifierLegacy/wrong_host_for_leaf"
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)

watchflakes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Status: No status
Development

No branches or pull requests

1 participant