From dc685b34fa9fd1123f95ae26103d535677130b95 Mon Sep 17 00:00:00 2001 From: 4gray Date: Mon, 28 Sep 2026 22:43:09 +0200 Subject: [PATCH] docs(coverage): say two-core runs keep two workers per project Co-Authored-By: Claude Opus 5.5 --- docs/architecture/validation-map.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/architecture/validation-map.md b/docs/architecture/validation-map.md index 327b2c38c..85fae5125 100644 --- a/docs/architecture/validation-map.md +++ b/docs/architecture/validation-map.md @@ -99,8 +99,9 @@ It runs projects a few at a time, largest first, with a bounded Jest worker count per project (defaults: `min(3, cores - 1)` in flight and `ceil(cores / concurrency)` workers each; override with `--concurrency=N`, `--max-workers=N` or `TIER_A_CONCURRENCY` / `TIER_A_MAX_WORKERS`). Two cores -stay serial: one worker per project runs Jest in-band, and a big project's -single heap can run out on a small machine; avoid `--max-workers=1`. Each +run one project at a time with two workers. Two in flight would leave each +project one worker, which runs Jest in-band, and a big project's single heap +can run out on a small machine; for the same reason avoid `--max-workers=1`. Each project's output is printed as one block when it finishes, and the run ends with the wall-clock total and the longest projects. Spec `tsconfig`s set `isolatedModules: true`, so ts-jest transpiles files one at a time instead of