fix: latency tests (#685)

Improve logic in latency tests as they might fail on busy machines
as the actual latency is longer than expected.

redis/reply_test.go

diff --git a/redis/reply_test.go b/redis/reply_test.go
index 5ff3b5f..3f1705b 100644
--- a/redis/reply_test.go
+++ b/redis/reply_test.go
@@ -264,13 +264,17 @@
 	require.Equal(t, 1, len(latestLatencies))
 
 	latencyEvent := latestLatencies[0]
+
+	// The actual latency might be longer than 1ms
+	require.GreaterOrEqual(t, latencyEvent.Latest, time.Millisecond)
+	require.GreaterOrEqual(t, latencyEvent.Max, time.Millisecond)
 	expected := redis.Latency{
 		Name:   "command",
-		Latest: time.Millisecond,
-		Max:    time.Millisecond,
+		Latest: latencyEvent.Latest,
+		Max:    latencyEvent.Max,
 		Time:   latencyEvent.Time,
 	}
-	require.Equal(t, latencyEvent, expected)
+	require.Equal(t, expected, latencyEvent)
 }
 
 func TestLatencyHistories(t *testing.T) {
@@ -315,7 +319,8 @@
 
 	require.Len(t, latencyHistory, 1)
 	latencyEvent := latencyHistory[0]
-	require.Equal(t, time.Millisecond, latencyEvent.ExecutionTime)
+	// The actual latency might be longer than 1ms
+	require.GreaterOrEqual(t, latencyEvent.ExecutionTime, time.Millisecond)
 }
 
 // dial wraps DialDefaultServer() with a more suitable function name for examples.