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
That test is designed to trigger a timeout. The close of the netConn in redis.DialContext should result in the TLS handshake returning an error but the test io.Reader never returns io.EOF so yes this is a leak but it's a leak in the test not the package.
Ensure that goroutines started by tests are cleaned up on termination.
Also:
* make TestLatencyHistories compatible with -count=X.
* Update to the supported versions of go 1.19 and 1.20.
* Update golangci-lint to v1.15.2
Fixes#641
When I run some test on https://github.com/gomodule/redigo/blob/master/redis/conn_test.go, I get the following output information when running TestDialTLSHandshakeTimeout:
So I was wondering if there is a goroutine leak in that case?
The text was updated successfully, but these errors were encountered: