Repository navigation
Flaky Test: test-child-process-fork-exec-path #54189
Description
Test
parallel.test-child-process-fork-exec-path
Platform
Windows
Console output
---
duration_ms: 3901.991
exitcode: 1
severity: fail
stack: |-
Can't clean tmpdir: d:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.112
Files blocking: [ 'node-copy.exe' ]
d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:69
throw e;
^
Error: EPERM, Permission denied: \\?\d:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.112 '\\?\d:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.112'
at Object.rmSync (node:fs:1246:18)
at rmSync (d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:20:8)
at onexit (d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:54:5)
at process.<anonymous> (d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:43:14)
at process.emit (node:events:532:35) {
errno: 1,
code: 'EPERM',
path: '\\\\?\\d:\\workspace\\node-test-binary-windows-js-suites\\node\\test\\.tmp.112',
syscall: 'rm'
}
Node.js v23.0.0-pre
...Build links
Additional information
No response
Activity
StefanStojanovic commentedon Aug 6, 2024
This test is not flaky. It was failing because of some changes in the build system, which were later reverted. For more details on this issue, please see this and this. Leaving this issue opened for now as an extra safety measurement. Will close it in a few days if it doesn't happen again.
pmarchini commentedon Aug 6, 2024
Thanks @StefanStojanovic
StefanStojanovic commentedon Aug 15, 2024
Closing the issue since it is now fixed.