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
I observed that the withConn tests in internal_test.go often fail due to connection errors. Interestingly, they tend to pass in the CI environment.
Details:
The tests are designed to establish a connection to Redis at 127.0.0.1:6379, but the test setup does not initiate a Redis server. In the CI pipeline, these tests succeed because another Redis instance is running for a different test case.
Additionally, it's worth noting that these withConn tests are located within the Redis package, rather than in redis_test, where the BeforeSuite function initializes Redis.
The text was updated successfully, but these errors were encountered:
I observed that the withConn tests in internal_test.go often fail due to connection errors. Interestingly, they tend to pass in the CI environment.
Details:
The tests are designed to establish a connection to Redis at 127.0.0.1:6379, but the test setup does not initiate a Redis server. In the CI pipeline, these tests succeed because another Redis instance is running for a different test case.
Additionally, it's worth noting that these withConn tests are located within the Redis package, rather than in redis_test, where the BeforeSuite function initializes Redis.
The text was updated successfully, but these errors were encountered: