Skip to content

Commit fc73e02

Browse files
committed
fix(mollifier): raise mollifierGate test timeout to 30s for postgresTest startup
The per-org isolation suite uses `postgresTest`, which spins up a fresh Postgres testcontainer per case. On CI the 5s vitest default regularly times out on container start before the test body runs. Match the 30s `vi.setConfig` used by other postgresTest suites in this app.
1 parent 86b9ec7 commit fc73e02

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

apps/webapp/test/mollifierGate.test.ts

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,11 @@ import {
2222
} from "~/v3/mollifier/mollifierGate.server";
2323
import type { DecisionOutcome, DecisionReason } from "~/v3/mollifier/mollifierTelemetry.server";
2424

25+
// Each `postgresTest` boots its own Postgres container; the 5s vitest default
26+
// regularly times out on CI just on container start. Match the timeout used by
27+
// other postgresTest suites in this app (e.g. `taskIdentifierRegistry.test.ts`).
28+
vi.setConfig({ testTimeout: 30_000 });
29+
2530
// We deliberately don't use vi.fn here. Per repo policy tests shouldn't lean on
2631
// mock frameworks for behaviours that are pure functions of the inputs — the
2732
// gate is pure decision logic, so a hand-rolled "deps + spy log" wired with

0 commit comments

Comments
 (0)