Bound targeted runner process and thread fan-out #176
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/image-gate-nested-process"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bound nested selected-test execution without removing process isolation or tests: serial files, V8/libuv/esbuild pools of one. Preserve causal failure and prerequisite failure propagation.
Linux Node24.22.1 under 2g/2CPU/pids256: identical204 background sleeps, baseline5/6 with esbuild newosproc errno11 and pids.events max40; candidate6/6, pids.events max0. This reproduces PID exhaustion, not the exact historical hosted SIGABRT.
Full local diagnostic remains red: candidate1017/1023, baseline also has cron/evaluator/scheduler failures; additional candidate dispatcher timing failure. No gate waiver or hosted acceptance claimed. No security/resource-limit expansion.
Exact-head Linux gate verified: Node24.22.1,2GiB/2CPUs/256PIDs,UID1000,capdropALL,nonewpriv, executable /tmp. Full1023/1023 and targeted6/6; typecheck/build exit0. No tests skipped. Controlled PID-pressure red/green proven; historical SIGABRT cause not proven. Integrating tested repair through separate nonauthor identity; hosted image acceptance remains pending.