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.
This commit is contained in:
go0p
2026-08-18 14:42:34 +08:00
parent 78b0c6befd
commit 3c7d4bfd41
@@ -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(