Investigate flaky test-trace-events-fs-sync

[F3n67u]

Test

test-trace-events-fs-sync

Platform

windows

Console output

C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-trace-events-fs-sync.js:133
    throw new Error(`${tr}:\n${util.inspect(proc)}`);
    ^

Error: fs.sync.fstat:
{
  status: 1,
  signal: null,
  output: [
    null,
    '',
    'node:internal/fs/utils:347\r\n' +
      '    throw err;\r\n' +
      '    ^\r\n' +
      '\r\n' +
      "Error: EPERM: operation not permitted, open 'fs.txt'\r\n" +
      '    at Object.openSync (node:fs:599:3)\r\n' +
      '    at Object.writeFileSync (node:fs:2221:35)\r\n' +
      '    at [eval]:1:4\r\n' +
      '    at Script.runInThisContext (node:vm:130:12)\r\n' +
      '    at Object.runInThisContext (node:vm:306:38)\r\n' +
      '    at node:internal/process/execution:76:19\r\n' +
      '    at [eval]-wrapper:6:22\r\n' +
      '    at evalScript (node:internal/process/execution:75:60)\r\n' +
      '    at node:internal/main/eval_string:27:3 {\r\n' +
      '  errno: -4048,\r\n' +
      "  syscall: 'open',\r\n" +
      "  code: 'EPERM',\r\n" +
      "  path: 'fs.txt'\r\n" +
      '}\r\n' +
      '\r\n' +
      'Node.js v19.0.0-pre\r\n'
  ],
  pid: 2124,
  stdout: '',
  stderr: 'node:internal/fs/utils:347\r\n' +
    '    throw err;\r\n' +
    '    ^\r\n' +
    '\r\n' +
    "Error: EPERM: operation not permitted, open 'fs.txt'\r\n" +
    '    at Object.openSync (node:fs:599:3)\r\n' +
    '    at Object.writeFileSync (node:fs:2221:35)\r\n' +
    '    at [eval]:1:4\r\n' +
    '    at Script.runInThisContext (node:vm:130:12)\r\n' +
    '    at Object.runInThisContext (node:vm:306:38)\r\n' +
    '    at node:internal/process/execution:76:19\r\n' +
    '    at [eval]-wrapper:6:22\r\n' +
    '    at evalScript (node:internal/process/execution:75:60)\r\n' +
    '    at node:internal/main/eval_string:27:3 {\r\n' +
    '  errno: -4048,\r\n' +
    "  syscall: 'open',\r\n" +
    "  code: 'EPERM',\r\n" +
    "  path: 'fs.txt'\r\n" +
    '}\r\n' +
    '\r\n' +
    'Node.js v19.0.0-pre\r\n'
}
    at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-trace-events-fs-sync.js:133:11)
    at Module._compile (node:internal/modules/cjs/loader:1116:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1170:10)
    at Module.load (node:internal/modules/cjs/loader:994:32)
    at Module._load (node:internal/modules/cjs/loader:834:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47

Node.js v19.0.0-pre

Build links

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

Additional information

This flaky test has been reported on those closed issues:

#25512, #22865, #22238, #21038

query this test nodejs/reliability: https://github.com/nodejs/reliability/issues?q=is%3Aissue+is%3Aopen+test-trace-events-fs-sync

[bnoordhuis]

Making each sub-test operate on a unique file name will probably fix this. Right now they all open, modify and unlink a file called fs.txt. Unlink on Windows can put the file in limbo for a short while where it's almost-but-not-quite gone.