Inspector tests fail when current path has encoded characters (like ~)

[kapouer]

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

[kapouer]

I'm currently making sure this was the right analysis...

[richardlau]

@kapouer Do you have any example failure output (build log?)?

[kapouer]

Here
search for "not ok"

[kapouer]

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]

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.

we have updated llhttp in this release to 9.3.0, that could be why?

[kapouer]

The problem is...
Test fails when run from this path: /build/reproducible-path/nodejs-20.19.5+dfsg+~cs20.19.12
and succeeds when run from this path: /build/reproducible-path/nodejs-20.19.5
🤔

[kapouer]

I could reproduce with node-v20.19.5-linux-x64.tar.xz downloaded from nodejs.org

[kapouer]

Reproduced with node-v22.19.0-linux-x64.tar.xz, node-v24.8.0-linux-x64.tar.xz too.