parallel/test-assert-esm-cjs-message-verify is flaky #53962
Description
Test
parallel/test-assert-esm-cjs-message-verify
Platform
Linux PPC64LE, Linux s390x, Linux x64
Console output
00:56:31 not ok 18 parallel/test-assert-esm-cjs-message-verify 00:56:31 --- 00:56:31 duration_ms: 330.23900 00:56:31 severity: fail 00:56:31 exitcode: 1 00:56:31 stack: |- 00:56:31 TAP version 13 00:56:31 # Subtest: ensure the assert.ok throwing similar error messages for esm and cjs files 00:56:31 # Subtest: should return code 1 for each command 00:56:31 ok 1 - should return code 1 for each command 00:56:31 --- 00:56:31 duration_ms: 129.378294 00:56:31 ... 00:56:31 1..1 00:56:31 not ok 1 - ensure the assert.ok throwing similar error messages for esm and cjs files 00:56:31 --- 00:56:31 duration_ms: 132.938811 00:56:31 type: 'suite' 00:56:31 location: '/home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-assert-esm-cjs-message-verify.js:26:1' 00:56:31 failureType: 'hookFailed' 00:56:31 error: "EEXIST: file already exists, mkdir '/home/iojs/node-tmp/.tmp.15'" 00:56:31 code: 'EEXIST' 00:56:31 stack: |- 00:56:31 Object.mkdirSync (node:fs:1359:26) 00:56:31 Object.refresh (/home/iojs/build/workspace/node-test-commit-linux/test/common/tmpdir.js:36:6) 00:56:31 SuiteContext.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-assert-esm-cjs-message-verify.js:49:12) 00:56:31 TestHook.runInAsyncScope (node:async_hooks:206:9) 00:56:31 TestHook.run (node:internal/test_runner/test:866:25) 00:56:31 TestHook.run (node:internal/test_runner/test:1117:18) 00:56:31 TestHook.run (node:internal/util:545:20) 00:56:31 node:internal/test_runner/test:786:20 00:56:31 process.processTicksAndRejections (node:internal/process/task_queues:95:5) 00:56:31 async Suite.runHook (node:internal/test_runner/test:784:7) 00:56:31 ... 00:56:31 1..1 00:56:31 # tests 1 00:56:31 # suites 1 00:56:31 # pass 1 00:56:31 # fail 0 00:56:31 # cancelled 0 00:56:31 # skipped 0 00:56:31 # todo 0 00:56:31 # duration_ms 144.242093 00:56:31 ...Build links
- https://ci.nodejs.org/job/node-test-commit-linux/58949/nodes=fedora-last-latest-x64/
- https://ci.nodejs.org/job/node-test-commit-linux/59028/nodes=ubuntu2204-64/
- https://ci.nodejs.org/job/node-test-commit-linuxone/44591/nodes=rhel8-s390x/
- https://ci.nodejs.org/job/node-test-commit-plinux/54294/nodes=rhel9-ppc64le/
- https://ci.nodejs.org/job/node-test-commit-plinux/54309/nodes=rhel9-ppc64le/
Additional information
This shows up in today's Reliability report https://github.com/nodejs/reliability/actions/runs/10015836224 (issue creation failed because the "body is too long (maximum is 65536 characters"):
It looks like the test sporadically failed on Windows previously (according to past reliability reports) but the Linux failures are only showing up in today's report.
I can also reproduce this locally on Linux x64 (RHEL 9) with
./tools/test.py --repeat 1000 -J parallel/test-assert-esm-cjs-message-verify Failures rates vary (seeing anything between 4-10 failures per 1000 runs).