From 7b0b08cbe35903a2177420fc0128835a07607792 Mon Sep 17 00:00:00 2001 From: Derek Collison Date: Mon, 6 Jan 2025 17:47:10 -0500 Subject: [PATCH] De-flake TestJetStreamClusterRedeliverBackoffs (#6331) `TestJetStreamClusterRedeliverBackoffs` would sometimes fail, even though it would be very close to the intended backoff: ``` jetstream_cluster_2_test.go:4216: Timing is off for 1, expected ~100ms, but got 99.846642ms jetstream_cluster_2_test.go:4216: Timing is off for 0, expected ~25ms, but got 50.767748ms jetstream_cluster_2_test.go:4216: Timing is off for 4, expected ~250ms, but got 249.95211ms ``` Allowing for a bit of leeway on both ends. Signed-off-by: Maurice van Veen --- server/jetstream_cluster_2_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/jetstream_cluster_2_test.go b/server/jetstream_cluster_2_test.go index 5807786e625..bda2200755b 100644 --- a/server/jetstream_cluster_2_test.go +++ b/server/jetstream_cluster_2_test.go @@ -4219,7 +4219,7 @@ func TestJetStreamClusterRedeliverBackoffs(t *testing.T) { d := tr.Sub(start) // Adjust start for next calcs. start = start.Add(d) - if d < expected[i] || d > expected[i]*2 { + if d < expected[i]-5*time.Millisecond || d > expected[i]*2+5*time.Millisecond { t.Fatalf("Timing is off for %d, expected ~%v, but got %v", i, expected[i], d) } }