From 3c7d4bfd4101b3f2a4b8e0e766d41ae3e7078db6 Mon Sep 17 00:00:00 2001 From: go0p Date: Tue, 18 Aug 2026 14:42:34 +0800 Subject: [PATCH] test: raise timeout for the budget-trimming recording test on slow CI runners The test builds ~1MiB of events per tab to exercise the global retention budget, which takes ~3.5s locally and exceeds the default 5s timeout on slower CI hardware. --- src/features/browser-recording/service.test.ts | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/features/browser-recording/service.test.ts b/src/features/browser-recording/service.test.ts index c9c33ec..fd9a525 100644 --- a/src/features/browser-recording/service.test.ts +++ b/src/features/browser-recording/service.test.ts @@ -219,7 +219,9 @@ describe('browser recording storage, snapshot and retained-value budgets', () => expect(snapshot.status.retainedCallBytes).toBe(4_096); }); - it('drops the globally oldest events to keep each snapshot and all sessions bounded', async () => { + // The budget-trimming path needs ~1MiB of events per tab, which alone takes + // seconds on CI hardware; the data volume is the point of the test. + it('drops the globally oldest events to keep each snapshot and all sessions bounded', { timeout: 30_000 }, async () => { const service = await freshService(); for (let tabId = 10; tabId < 15; tabId += 1) { fixture.pages.set(tabId, rawSnapshot(