From cafeae4ecd841e9126fce4047421e7305349c903 Mon Sep 17 00:00:00 2001 From: Noah Treuhaft Date: Mon, 19 Sep 2016 15:30:32 -0700 Subject: [PATCH] Fix connection pool exhaustion in Redis tests The Redis tests were failing with a "connection pool exhausted" error from Redigo. Closing the connection used for FLUSHDB fixes the problem. Signed-off-by: Noah Treuhaft --- registry/storage/cache/redis/redis_test.go | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/registry/storage/cache/redis/redis_test.go b/registry/storage/cache/redis/redis_test.go index 81bcaddd..d324842d 100644 --- a/registry/storage/cache/redis/redis_test.go +++ b/registry/storage/cache/redis/redis_test.go @@ -26,7 +26,7 @@ func TestRedisBlobDescriptorCacheProvider(t *testing.T) { if redisAddr == "" { // skip if still not set - t.Skip("please set -registry.storage.cache.redis to test layer info cache against redis") + t.Skip("please set -test.registry.storage.cache.redis.addr to test layer info cache against redis") } pool := &redis.Pool{ @@ -43,9 +43,11 @@ func TestRedisBlobDescriptorCacheProvider(t *testing.T) { } // Clear the database - if _, err := pool.Get().Do("FLUSHDB"); err != nil { + conn := pool.Get() + if _, err := conn.Do("FLUSHDB"); err != nil { t.Fatalf("unexpected error flushing redis db: %v", err) } + conn.Close() cachecheck.CheckBlobDescriptorCache(t, NewRedisBlobDescriptorCacheProvider(pool)) }