From a03426d5cac75a356e0da0fd56ab9ecb8e3a8d0f Mon Sep 17 00:00:00 2001
From: Diego Rodrigues de Sa e Souza
 <8016841+diegosouzapw@users.noreply.github.com>
Date: Mon, 15 Jun 2026 19:37:57 -0300
Subject: [PATCH] test: reconcile runtime-timeouts keepAlive baseline to 4000
 after #3907 source revert (#3933)

PR #3907 lowered the test assertions for fetchKeepAliveTimeoutMs from 4000 to
1000 expecting DEFAULT_FETCH_KEEPALIVE_TIMEOUT_MS to drop to 1000, but the source
change was reverted on review (kept at 4000, with keepAliveMaxTimeout pinning
instead). The test was left asserting 1000, turning the unit suite red
release-wide. Align the assertions back to the shipped source value (4000).
---
 tests/unit/runtime-timeouts.test.ts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/unit/runtime-timeouts.test.ts b/tests/unit/runtime-timeouts.test.ts
index e67f82ee6a..1947411b78 100644
--- a/tests/unit/runtime-timeouts.test.ts
+++ b/tests/unit/runtime-timeouts.test.ts
@@ -17,7 +17,7 @@ test("upstream timeout config derives hidden fetch timeouts from FETCH_TIMEOUT_M
     fetchHeadersTimeoutMs: 600000,
     fetchBodyTimeoutMs: 600000,
     fetchConnectTimeoutMs: 30000,
-    fetchKeepAliveTimeoutMs: 1000,
+    fetchKeepAliveTimeoutMs: 4000,
   });
 });
 
@@ -54,7 +54,7 @@ test("upstream timeout config honors explicit overrides and falls back on invali
   assert.equal(config.fetchHeadersTimeoutMs, 610000);
   assert.equal(config.fetchBodyTimeoutMs, 0);
   assert.equal(config.fetchConnectTimeoutMs, 45000);
-  assert.equal(config.fetchKeepAliveTimeoutMs, 1000);
+  assert.equal(config.fetchKeepAliveTimeoutMs, 4000);
 });
 
 test("TLS client timeout defaults to FETCH_TIMEOUT_MS and can be overridden", () => {