You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, our GRPC tests are flaky, and currently, in most cases, the test pipeline will fail with errors like (but generally check the latest piplines):
Error: "GoError: context deadline exceeded: connection error: desc = \"transport: failed to write client preface: write tcp 127.0.0.1:55164->127.0.0.1:43483: write: connection reset by peer\" at reflect.methodValueCall (native)" does not contain "remote error: tls: bad certificate"
The affected tests belong to the client_test.go e.g. TestClient_TlsParameters
We need to investigate and fix the tests.
The grafana/k6 is also affected, so once the fix is found and applied, it should be backported back to the main k6 repository.
Why?
These flaky tests decrease the trust in the test suite and generally hurt the developer experience.
The text was updated successfully, but these errors were encountered:
After some investigation, I found that negative path tests rely on the timeout, like the test uses the wrong certificate, and we expect to get the error message, but it happens only when the timeout happens (context canceled).
After chasing the case, I think that the root cause of the issue is that the grpc library isn't treating such errors as permanent ones and is trying to retry. So I've ended up opening the issue grpc/grpc-go#6593
What?
Unfortunately, our GRPC tests are flaky, and currently, in most cases, the test pipeline will fail with errors like (but generally check the latest piplines):
The affected tests belong to the
client_test.go
e.g.TestClient_TlsParameters
We need to investigate and fix the tests.
The grafana/k6 is also affected, so once the fix is found and applied, it should be backported back to the main k6 repository.
Why?
These flaky tests decrease the trust in the test suite and generally hurt the developer experience.
The text was updated successfully, but these errors were encountered: