Repository navigation
Inspector tests fail when current path has encoded characters (like ~) #59803
Description
Version
20.19.5
Platform
Linux debian (the debian version)
Subsystem
test
What steps will reproduce the bug?
Run these parallel tests:
test-inspector.js
test-inspector-async-context-brk.js
test-inspector-bindings.js
test-inspector-multisession-js.js
test-runner-inspect.mjs
test-runner-coverage.js
test-startup-empty-regexp-statics.js
test-inspector-connect-main-thread.js
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
Tests pass
What do you see instead?
Tests fail.
Additional information
The commit that makes them fail comes from:
#57498
Activity
kapouer commentedon Sep 8, 2025
I'm currently making sure this was the right analysis...
richardlau commentedon Sep 8, 2025
@kapouer Do you have any example failure output (build log?)?
kapouer commentedon Sep 8, 2025
Here
search for "not ok"
kapouer commentedon Sep 8, 2025
Note that this is the version with shared libraries, and also it's the first time I try to use shared llhttp,
I may have shot myself in the foot.
marco-ippolito commentedon Sep 10, 2025
we have updated llhttp in this release to 9.3.0, that could be why?
kapouer commentedon Sep 17, 2025
The problem is...
Test fails when run from this path:
/build/reproducible-path/nodejs-20.19.5+dfsg+~cs20.19.12and succeeds when run from this path:
/build/reproducible-path/nodejs-20.19.5🤔
kapouer commentedon Sep 17, 2025
I could reproduce with node-v20.19.5-linux-x64.tar.xz downloaded from nodejs.org
[-]Failing inspector tests in 20.x branch[/-][+]Inspector tests fail when current path has encoded characters (like ~)[/+]kapouer commentedon Sep 18, 2025
Reproduced with node-v22.19.0-linux-x64.tar.xz, node-v24.8.0-linux-x64.tar.xz too.
github-actions commentedon Apr 19, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon May 19, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.