flakey unit test: Test_server_ClientCert/*
michel-laterman opened this issue · 1 comments
michel-laterman commented
Flaky Test
Effects main, example here
File here
It looks like it is where the request may get a connection refused response
Stack Trace
=== RUN Test_server_ClientCert/valid_client_certs_no_certs_requested
--
| server_test.go:349:
| Error Trace: /opt/buildkite-agent/builds/bk-agent-prod-gcp-1707490899215587797/elastic/fleet-server/internal/pkg/api/server_test.go:349
| Error: Received unexpected error:
| Get "https://localhost:36805/api/status": dial tcp 127.0.0.1:36805: connect: connection refused
| Test: Test_server_ClientCert/valid_client_certs_no_certs_requested
michel-laterman commented
More logs
=== RUN Test_server_ClientCert/valid_client_certs_no_certs_requested
--
| server.go:175: {"level":"info","message":"server hard connection limiter disabled"}
| server_test.go:354:
| Error Trace: /opt/buildkite-agent/builds/bk-agent-prod-gcp-1707983859488530268/elastic/fleet-server/internal/pkg/api/server_test.go:354
| Error: Received unexpected error:
| Get "https://localhost:45963/api/status": dial tcp 127.0.0.1:45963: connect: connection refused
| Test: Test_server_ClientCert/valid_client_certs_no_certs_requested
| FAIL: Test_server_ClientCert (3.61s)