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?
to your account
--- FAIL: TestVerifyHostnameResumed (1.53s)
--- FAIL: TestVerifyHostnameResumed/TLSv13 (0.51s)
tls_test.go:381: Subsequent connection unexpectedly didn't resume
FAIL crypto/tls 2.430s
It started at seemingly unrelated https://go-review.googlesource.com/c/go/+/176925 (cmd/go) and persisted the following three commits.
Does this test depend on the network? Did some peer change its behavior?
The text was updated successfully, but these errors were encountered:
Yeah the GFEs started bundling session tickets with the first flight, I think. Sent a fix.
Sorry, something went wrong.
Sent a fix
Sent a fix
Where? I don't see one at https://go-review.googlesource.com/q/owner:filippo%2540golang.org
Change https://golang.org/cl/177877 mentions this issue: crypto/tls: fix TestVerifyHostnameResumed
crypto/tls: fix TestVerifyHostnameResumed
remote: The push has been rejected because we detect that it contains a private
remote: key. Please check the following commands and confirm that it's
No branches or pull requests