From dc25aafc80c7ee462df77bb63fae9269b956332f Mon Sep 17 00:00:00 2001 From: paschal533 Date: Fri, 17 Apr 2026 12:30:49 +0100 Subject: [PATCH] fix(interface-compliance-tests): increase abort propagation timeout in stream muxer close test MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 70ms timeout races against delay(10) loop iterations: dialer.abort() fires at t=50ms leaving only 20ms for propagation. On loaded CI runners, Node.js timer imprecision routinely exceeds this margin, causing spurious failures. 2000ms is a generous upper bound — on success the test exits well under 100ms; the timeout only fires if abort genuinely fails to propagate. --- .../interface-compliance-tests/src/stream-muxer/close-test.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/interface-compliance-tests/src/stream-muxer/close-test.ts b/packages/interface-compliance-tests/src/stream-muxer/close-test.ts index 3f6abd4596..c3e10d527e 100644 --- a/packages/interface-compliance-tests/src/stream-muxer/close-test.ts +++ b/packages/interface-compliance-tests/src/stream-muxer/close-test.ts @@ -195,7 +195,7 @@ export default (common: TestSetup): void => { new Promise((resolve, reject) => { setTimeout(() => { reject(timeoutError) - }, 70) + }, 2000) }) ]) expect.fail('stream pipe with infinite source should never return')