`parallel/test-runner-cli-concurrency` fails with `EBUSY: resource busy or locked`

[richardlau]

Test

parallel/test-runner-cli-concurrency

Platform

Windows

Console output

08:25:15 not ok 648 parallel/test-runner-cli-concurrency
08:25:15   ---
08:25:15   duration_ms: 1568.01900
08:25:15   severity: fail
08:25:15   exitcode: 1
08:25:15   stack: |-
08:25:15     TAP version 13
08:25:15     # Subtest: concurrency of one
08:25:15     ok 1 - concurrency of one
08:25:15       ---
08:25:15       duration_ms: 1120.0039
08:25:15       ...
08:25:15     # Subtest: concurrency of two
08:25:15     not ok 2 - concurrency of two
08:25:15       ---
08:25:15       duration_ms: 1.3672
08:25:15       location: 'C:\\workspace\\node-test-binary-windows-js-suites\\node\\test\\parallel\\test-runner-cli-concurrency.js:36:1'
08:25:15       failureType: 'hookFailed'
08:25:15       error: "EBUSY: resource busy or locked, rmdir '\\\\?\\C:\\workspace\\node-test-binary-windows-js-suites\\node\\test\\.tmp.644'"
08:25:15       code: 'EBUSY'
08:25:15       stack: |-
08:25:15         rmdirSync (node:fs:1232:10)
08:25:15         _rmdirSync (node:internal/fs/rimraf:235:5)
08:25:15         rimrafSync (node:internal/fs/rimraf:193:7)
08:25:15         Object.rmSync (node:fs:1281:10)
08:25:15         rmSync (C:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:20:8)
08:25:15         Object.refresh (C:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:35:3)
08:25:15         TestContext.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-runner-cli-concurrency.js:20:10)
08:25:15         TestHook.runInAsyncScope (node:async_hooks:206:9)
08:25:15         TestHook.run (node:internal/test_runner/test:631:25)
08:25:15         TestHook.run (node:internal/test_runner/test:856:18)
08:25:15       ...
08:25:15     1..2
08:25:15     # tests 2
08:25:15     # suites 0
08:25:15     # pass 1
08:25:15     # fail 1
08:25:15     # cancelled 0
08:25:15     # skipped 0
08:25:15     # todo 0
08:25:15     # duration_ms 1136.2309
08:25:15     Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.644
08:25:15     Files blocking: [ 'test-2.js' ]
08:25:15     
08:25:15     C:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:69
08:25:15         throw e;
08:25:15         ^
08:25:15     
08:25:15     Error: EBUSY: resource busy or locked, rmdir '\\?\C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.644'
08:25:15         at rmdirSync (node:fs:1232:10)
08:25:15         at _rmdirSync (node:internal/fs/rimraf:235:5)
08:25:15         at rimrafSync (node:internal/fs/rimraf:193:7)
08:25:15         at Object.rmSync (node:fs:1281:10)
08:25:15         at rmSync (C:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:20:8)
08:25:15         at onexit (C:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:54:5)
08:25:15         at process.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:43:14)
08:25:15         at process.emit (node:events:527:35) {
08:25:15       errno: -4082,
08:25:15       syscall: 'rmdir',
08:25:15       code: 'EBUSY',
08:25:15       path: '\\\\?\\C:\\workspace\\node-test-binary-windows-js-suites\\node\\test\\.tmp.644'
08:25:15     }
08:25:15     
08:25:15     Node.js v21.0.0-pre
08:25:15   ...

Build links

• https://ci.nodejs.org/job/node-test-binary-windows-js-suites/23646/

Additional information

parallel/test-runner-cli-concurrency was added by #49996 yesterday and failed in today's daily build.

Given file deletion is involved, this is probably a case of file deletion semantics on Windows being different to POSIX, see https://www.youtube.com/watch?v=uhRWMGBjlO8&t=534s.