You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
parallel/test-config-file address already in use #59152
not ok 934 parallel/test-config-file --- duration_ms: 8774.08300 severity: fail exitcode: 1 stack: |- Test failure: '--inspect=true should be parsed correctly' Location: test/parallel/test-config-file.js:237:1 AssertionError [ERR_ASSERTION]: The input did not match the regular expression /^Debugger listening on (ws:\/\/[^\s]+)/. Input: 'Starting inspector on 127.0.0.1:9229 failed: address already in use\n' at TestContext.<anonymous> (/tmp/nodejs.f6r/test/parallel/test-config-file.js:244:3) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async Test.run (node:internal/test_runner/test:1054:7) at async Test.processPendingSubtests (node:internal/test_runner/test:744:7) { generatedMessage: true, code: 'ERR_ASSERTION', actual: 'Starting inspector on 127.0.0.1:9229 failed: address already in use\n', expected: /^Debugger listening on (ws:\/\/[^\s]+)/, operator: 'match' }
Build links
Private CI
Additional information
Retries eventually succeed so I'm pretty sure this is a race condition with another test that opens the inspector
Activity
richardlau commentedon Jul 21, 2025
This should be fixed by #58799. It's on the
v22.x-stagingbranch, pending the next Node.js 22 release.marco-ippolito commentedon Aug 1, 2025
The fix has been released in v22.18.0 so I guess we can close it