It seems test-child-process-exec-abortcontroller-promisified doesn't cleanup correct as I see 2 running node.js processes afterwards.
On my local windows I see two instances of node.exe" -e "setInterval(()=>{}, 99)" after this test.
ProcessExplorer shows they are in suspended state.
Seems like the actual cause are the last two tests where AbortSignal.abort(err) is done before calling execPromisifed.
Not sure if this is just at test problem or a real bug.
It seems test-child-process-exec-abortcontroller-promisified doesn't cleanup correct as I see 2 running node.js processes afterwards.
On my local windows I see two instances of
node.exe" -e "setInterval(()=>{}, 99)"after this test.ProcessExplorer shows they are in suspended state.
Seems like the actual cause are the last two tests where
AbortSignal.abort(err)is done before callingexecPromisifed.Not sure if this is just at test problem or a real bug.