childprocess kill() results in -4048 EPERM error on windows since update to v21.6.2

[Uzlopak]

Version

v21.6.2

Platform

Microsoft Windows NT 10.0.22621.0 x64

Subsystem

child_process

What steps will reproduce the bug?

Suddenly in latest undici the tests in test/node-test/debug.js fail if run under windows with node v21.6.2.

It fails under PowerShell and cmd.

It seems that there is suddenly a permission issue when trying to kill a child_process. With node v21.6.1 .kill() doesnt throw.

How often does it reproduce? Is there a required condition?

Always reproducable

What is the expected behavior? Why is that the expected behavior?

Should not throw (and close the child process)

What do you see instead?

PS C:\Users\Aras\Desktop\undici> node .\test\node-test\debug.js
✖ debug#websocket (175.6675ms)
  Error: kill EPERM
      at ChildProcess.kill (node:internal/child_process:512:26)
      at TestContext.<anonymous> (C:\Users\Aras\Desktop\undici\test\node-test\debug.js:48:9)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async Test.run (node:internal/test_runner/test:632:9)
      at async startSubtest (node:internal/test_runner/harness:218:3) {
    errno: -4048,
    code: 'EPERM',
    syscall: 'kill'
  }

✖ debug#fetch (174.8844ms)
  Error: kill EPERM
      at ChildProcess.kill (node:internal/child_process:512:26)
      at TestContext.<anonymous> (C:\Users\Aras\Desktop\undici\test\node-test\debug.js:83:9)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async Test.run (node:internal/test_runner/test:632:9)
      at async Test.processPendingSubtests (node:internal/test_runner/test:374:7) {
    errno: -4048,
    code: 'EPERM',
    syscall: 'kill'
  }

✖ debug#undici (150.1489ms)
  Error: kill EPERM
      at ChildProcess.kill (node:internal/child_process:512:26)
      at TestContext.<anonymous> (C:\Users\Aras\Desktop\undici\test\node-test\debug.js:121:9)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async Test.run (node:internal/test_runner/test:632:9)
      at async Test.processPendingSubtests (node:internal/test_runner/test:374:7) {
    errno: -4048,
    code: 'EPERM',
    syscall: 'kill'
  }

ℹ tests 3
ℹ suites 0
ℹ pass 0
ℹ fail 3
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 511.956

✖ failing tests:

test at test\node-test\debug.js:11:1
✖ debug#websocket (175.6675ms)
  Error: kill EPERM
      at ChildProcess.kill (node:internal/child_process:512:26)
      at TestContext.<anonymous> (C:\Users\Aras\Desktop\undici\test\node-test\debug.js:48:9)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async Test.run (node:internal/test_runner/test:632:9)
      at async startSubtest (node:internal/test_runner/harness:218:3) {
    errno: -4048,
    code: 'EPERM',
    syscall: 'kill'
  }

test at test\node-test\debug.js:51:1
✖ debug#fetch (174.8844ms)
  Error: kill EPERM
      at ChildProcess.kill (node:internal/child_process:512:26)
      at TestContext.<anonymous> (C:\Users\Aras\Desktop\undici\test\node-test\debug.js:83:9)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async Test.run (node:internal/test_runner/test:632:9)
      at async Test.processPendingSubtests (node:internal/test_runner/test:374:7) {
    errno: -4048,
    code: 'EPERM',
    syscall: 'kill'
  }

test at test\node-test\debug.js:86:1
✖ debug#undici (150.1489ms)
  Error: kill EPERM
      at ChildProcess.kill (node:internal/child_process:512:26)
      at TestContext.<anonymous> (C:\Users\Aras\Desktop\undici\test\node-test\debug.js:121:9)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async Test.run (node:internal/test_runner/test:632:9)
      at async Test.processPendingSubtests (node:internal/test_runner/test:374:7) {
    errno: -4048,
    code: 'EPERM',
    syscall: 'kill'
  }

Additional information

I assume that this bug is coming from libuv.

[targos]

@nodejs/libuv

[Uzlopak]

@targos

Should I open another issue in libuv?

[targos]

Maybe? I don't know if that would be relevant without a repro using libuv directly.

FWIW this commit changed the implementation of the uv_kill function on Windows: https://github.com/libuv/libuv/commit/129362f35648a61ab19ab665014d2013731a986b

@vtjnash

[mcollina]

@santigimeno could you take a look?

[santigimeno]

So, I think there's a regression in libuv which might be solved in https://github.com/libuv/libuv/pull/4341. Regardless, just curious why the need to call child.kill() in those tests as the child processes should exit gracefully.

[Uzlopak]

@santigimeno

It spins up the server and then kills it. Was this way for quiete a while. i could have patched it, but then I could not have report this bug ;)

[santigimeno]

This is fixed in libuv, so it'll be fixed once a new version reaches node.

[Uzlopak]

great job, thanks

[SimenB]

Is it correct that the update in libuv did not land in Node 22 either? Is there any timeline for this?

[Uzlopak]

I dont know. I just know that we patched our test in undici accordingly to not run into the issue again. So probably the bug exists still. Would need to check on a windows machine.