From 178122529574b7139992e60dc4be3d78fc2ff314 Mon Sep 17 00:00:00 2001 From: Juan Olveira Date: Fri, 26 Jun 2026 23:49:26 +0000 Subject: [PATCH] e2e: increase client route propagation timeout to reduce flakiness The client-side route checks in TestE2E_MultiClientIBRLAllocatedIP waited only 60s, while the device-level iBGP checks that precede them in the propagation chain allow 90s. Since routes reach clients only after the devices learn them and re-advertise over the client BGP session, under CI load the client checks could time out even when propagation was healthy. Align the client timeouts with the 90s used for the device checks. --- e2e/multi_client_ibrl_allocated_ip_test.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/e2e/multi_client_ibrl_allocated_ip_test.go b/e2e/multi_client_ibrl_allocated_ip_test.go index 56a192838a..08bee69d44 100644 --- a/e2e/multi_client_ibrl_allocated_ip_test.go +++ b/e2e/multi_client_ibrl_allocated_ip_test.go @@ -233,14 +233,14 @@ func runMultiClientIBRLAllocatedIPWorkflowTest(t *testing.T, log *slog.Logger, d return false } return strings.Contains(string(output), client2DZIP) - }, 60*time.Second, 1*time.Second, "client1 should have route to client2") + }, 90*time.Second, 1*time.Second, "client1 should have route to client2") require.Eventually(t, func() bool { output, err := client2.Exec(t.Context(), []string{"ip", "r", "list", "dev", "doublezero0"}) if err != nil { return false } return strings.Contains(string(output), client1DZIP) - }, 60*time.Second, 1*time.Second, "client2 should have route to client1") + }, 90*time.Second, 1*time.Second, "client2 should have route to client1") log.Debug("--> Clients have routes to each other") // Disconnect client1.