forked from molecule-ai/molecule-core
Molecule AI Fullstack Engineer
9456d1c5fd
The forks pool's implicit maxWorkers=1 (2-CPU runner) was insufficient to prevent concurrent jsdom worker cold-starts. Each jsdom worker allocates ~30-50 MB RSS at boot; multiple workers starting simultaneously exhaust available memory, causing 5 test files to fail with: [vitest-pool]: Failed to start forks worker for test files ... [vitest-pool-runner]: Timeout waiting for worker to respond Individual jsdom test files take 12-15 s in isolation and pass cleanly. Failures only occur when 51 files are run together through the pool. Fix: explicitly set maxWorkers:1 so a single worker processes all files sequentially, eliminating concurrent jsdom bootstrap memory pressure. With this change, all 51 files pass (was 46 pass + 5 fail), and suite duration improves from ~5070 s to ~1117 s because workers no longer compete for resources during startup. Ref: issue #148 Ref: vitest-pool investigation for issue #22 (canvas side) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| e2e | ||
| public | ||
| src | ||
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| components.json | ||
| Dockerfile | ||
| next.config.ts | ||
| package-lock.json | ||
| package.json | ||
| playwright.config.ts | ||
| playwright.staging.config.ts | ||
| postcss.config.js | ||
| tsconfig.json | ||
| vitest.config.ts | ||