Skip to content

test: fix flaky Windows CI failure in nextjs-runtime-discovery teardown #142

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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gaojude merged 1 commit into from
Jun 1, 2026
Merged

test: fix flaky Windows CI failure in nextjs-runtime-discovery teardown #142

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 test/unit/nextjs-runtime-discovery.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,9 @@ function forceKillProcessTree(proc: ChildProcess): void {
const FIXTURE_SOURCE = join(__dirname, "../fixtures/nextjs16-minimal")
const TEST_PORT = 3456
const SERVER_STARTUP_TIMEOUT = 180000
// Teardown kills the dev server and rm -rf's a temp dir containing a full
// node_modules; on Windows CI this can exceed vitest's default 10s hookTimeout.
const CLEANUP_TIMEOUT = 60000
const TEST_TIMEOUT = 240000

describe("nextjs-runtime-discovery", () => {
Expand Down Expand Up @@ -194,7 +197,7 @@ describe("nextjs-runtime-discovery", () => {
console.error("[Test] Failed to clean up temp directory:", error)
}
}
})
}, CLEANUP_TIMEOUT)

it(
"should discover Next.js server on non-standard port via process discovery",
Expand Down
Loading