Skip to content

test: give heavy wrapper tests a Windows timeout budget #436

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Brooooooklyn merged 1 commit into from
Oct 15, 2026
Merged

test: give heavy wrapper tests a Windows timeout budget #436

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion packages/void/test/unit/wrapper.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -502,7 +502,10 @@ describe('generated wrapper queue dispatch', () => {
});
});

describe('generateWrapper with migrations', () => {
// These tests bundle Workers and start workerd. Windows CI runners stall on disk and process start,
// so one test can take 20 seconds there. Keep the longer budget local to these tests.
const migrationTestTimeout = process.platform === 'win32' ? 60_000 : undefined;
describe('generateWrapper with migrations', { timeout: migrationTestTimeout }, () => {
const roots: Array<string> = [];
// Each new PGlite runs initdb, which can take seconds on CI. Run it once in this hook, with its
// own budget; each PostgreSQL test loads a fresh database from the initialized data directory.
Expand Down
Loading