You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 357639b
Browse filesBrowse the repository at this point in the historyBrowse files
fix(scripts): bound check:changed concurrency and step time
check:changed started every step at once, so on a machine with few cores,
little memory, or other work running, typecheck, knip and tests competed
until the host stalled. Steps now run through a limiter sized from the core
count and available memory (CHECK_CHANGED_CONCURRENCY overrides), typecheck
uses the same budget, and a step running past CHECK_CHANGED_TIMEOUT seconds
(default 900) is killed with its process tree and reported as TIMEOUT.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: docs/operations/development.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,8 +170,11 @@ files to packages with [ci-changes.cjs](../../.github/scripts/ci-changes.cjs), a
170
170
compares against the merge base with `origin/main`, or with a ref you pass. CI still runs the full
171
171
test suites and the jobs the summary lists, so a local pass does not promise a green CI run.
172
172
173
-
The steps run side by side, so a run takes about as long as its slowest step, usually knip's
174
-
exports pass at about 10 s. When the files are exactly those of the last passing run, it prints that
173
+
The steps run side by side, as many at once as the machine allows: one per two cores and per 6 GiB
174
+
of available memory. On a large machine a run takes about as long as its slowest step, usually
175
+
knip's exports pass at about 10 s. Set `CHECK_CHANGED_CONCURRENCY` to change the limit (`1` runs
176
+
the steps one by one). A step that runs past `CHECK_CHANGED_TIMEOUT` seconds (default 900) is
177
+
killed with every process it started and reported as `TIMEOUT`, not as a failing check. When the files are exactly those of the last passing run, it prints that
175
178
run's summary instead of running again. Any change to a file, the install, or a generated file runs
0 commit comments