Test
test/parallel/test-debugger-exceptions
Platform
macOS x64
Console output
--- stderr ---
/Users/runner/work/node/node/dir%20with $unusual"chars?'åß∂ƒ©∆¬…`/test/common/debugger.js:92
const timeoutErr = new Error(`Timeout (${TIMEOUT}) while waiting for ${pattern}`);
^
Error: Timeout (15000) while waiting for /break (?:on start )?in/i
at /Users/runner/work/node/node/dir%20with $unusual"chars?'åß∂ƒ©∆¬…`/test/common/debugger.js:92:28
at new Promise (<anonymous>)
at Object.waitFor (...debugger.js:67:14)
at Object.waitForInitialBreak (...debugger.js:116:18) {
output: '\n' +
'< Debugger listening on ws://127.0.0.1:62755/a822d49a-62a8-4382-9bb9-5914aee2f453\n' +
'< Debugger attached.\n' +
' ok\n' +
'debug> '
}
Node.js v27.0.0-pre
Command: out/Release/node "/Users/runner/work/node/node/dir%20with $unusual"chars?'åß∂ƒ©∆¬…`/test/parallel/test-debugger-exceptions.js"Build links
Additional information
The failure occurs specifically in the "Re-run test in a folder whose name contains unusual chars" CI step. The debugger attaches successfully but the expected break in ... line is never emitted - the process runs to completion instead of pausing at the initial break point. waitForInitialBreak then times out after 15s.
The special characters in the directory path (spaces, $, ", ?, ', Unicode, backticks) likely cause argument parsing or shell quoting issues when the debugger spawns its child process, causing --inspect-brk or the script path to be misinterpreted.
Not reproduced locally in a normal path , failure appears tied specifically to the unusual-chars directory used in CI.
Test
test/parallel/test-debugger-exceptions
Platform
macOS x64
Console output
Build links
Additional information
The failure occurs specifically in the "Re-run test in a folder whose name contains unusual chars" CI step. The debugger attaches successfully but the expected break in ... line is never emitted - the process runs to completion instead of pausing at the initial break point. waitForInitialBreak then times out after 15s.
The special characters in the directory path (spaces, $, ", ?, ', Unicode, backticks) likely cause argument parsing or shell quoting issues when the debugger spawns its child process, causing --inspect-brk or the script path to be misinterpreted.
Not reproduced locally in a normal path , failure appears tied specifically to the unusual-chars directory used in CI.