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
It seems that some other test running in parallel in the package calls CloseIdleConnections on the same client, which causes the error.
The default HTTP client is used in many places in Coder and the flake we're seeing here manifests in other tests too, like this one: #582.
I don't have a generic solution in mind, so for now I'm going to ensure waiting on the telemetry report channel times out without a panic so our CI can retry the test gracefully: coder/coder#17879
This PR ensures that waits on channels will time out according to the
test context, rather than waiting indefinitely. This should alleviate
the panic seen in coder/internal#645 and, if
the deadlock recurs, allow the test to be retried automatically in CI.
https://github.com/coder/coder/actions/runs/15061235780/job/42336654525
The text was updated successfully, but these errors were encountered: