test: use unusual chars in the path to ensure our tests are robust

[aduh95]

Hopefully our tests should work without assuming the repo is cloned in path that contains unusual chars.

[nodejs-github-bot]

Review requested:

• @nodejs/actions

[aduh95]

TIL GNU Make does not support files containing whitespaces nor %, that's… unexpected.

[targos]

Should we maybe avoid the hidden characters? I guess it's ok if GH only warns about them now but I don't want to see a permanent warning on the repo.

[aduh95]

Should we maybe avoid the hidden characters? I guess it's ok if GH only warns about them now but I don't want to see a permanent warning on the repo.

I'm pretty sure it's just about the branch name for this PR, not related to the content of this PR.

console.log("\u2020\u00A3\u00A7\u2122" === '†£§™'); // true

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.41%. Comparing base (47ad609) to head (522b401).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #48409      +/-   ##
==========================================
- Coverage   88.41%   88.41%   -0.01%     
==========================================
  Files         653      653              
  Lines      187437   187437              
  Branches    36079    36075       -4     
==========================================
- Hits       165730   165721       -9     
- Misses      14948    14952       +4     
- Partials     6759     6764       +5     

see 26 files with indirect coverage changes

[RedYetiDev]

Is there a reason why node isn't checked out directly into the weird path characters?

[aduh95]

Yes, #48409 (comment)