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 adf4d49
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ci): keep Node 24 from deadlocking in process.exit()
Build, mutation, e2e and ratchet jobs hung for hours in `npm ci` after it had printed its summary.
On the runner, the hung npm had no children and three threads left: the main thread joining the
last V8Worker, which waited forever. That is Node 24's exit deadlock (nodejs/node#64274): exit
joins V8's platform workers while a background Maglev/Sparkplug compile waits for the main thread.
In a throwaway workflow, 6 of 80 `npm ci` runs hung on Node 24.21; with --no-maglev
--no-concurrent-sparkplug, 0 of 80.
NODE_OPTIONS does not take those flags, so a composite action puts a `node` shim first on PATH
right after setup-node, and checks that it is active. npm starts through `#!/usr/bin/env node`, so
npm and every node its scripts run go through it. The Docker builder stage gets the same shim in
/usr/local/sbin (created; the Alpine image lacks it), checked the same way. Remove both once Node
ships the fix.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments