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

okhttp: Workaround SSLSocket not noticing socket is closed #11266

Merged
merged 1 commit into from
Jun 6, 2024

Conversation

ejona86
Copy link
Member

@ejona86 ejona86 commented Jun 6, 2024

Using --runs_per_test=1000, this changes the flake rate of TlsTest from 2% to 0%.

While I believe it is possible to write a reliable test for this (including noticing the SSLSocket behavior), it was becoming too invasive so I gave up.

Fixes #11012

CC @larry-safran

Using --runs_per_test=1000, this changes the flake rate of TlsTest from
2% to 0%.

While I believe it is possible to write a reliable test for this
(including noticing the SSLSocket behavior), it was becoming too
invasive so I gave up.

Fixes grpc#11012
@ejona86 ejona86 requested a review from temawi June 6, 2024 00:02
@ejona86 ejona86 merged commit a28357e into grpc:master Jun 6, 2024
14 of 15 checks passed
@ejona86 ejona86 deleted the okhttp-tlstest-flaky branch June 6, 2024 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

io.grpc.okhttp.TlsTest hostnameVerifierFails_fails is flaky
2 participants