I have a PR that i'd like to submit but I can't get a valid dev setup to pass ALL of the tests (like over 100 do pass, but 37 fail...) right out of the box. My setup is not overly customized.
The PR addresses issues with default node version not being "sticky", there is an open issue for that. I got it fixed by directly patching the relevant files and thought I'd share the love.
Note: I have not altered the dev folder in any way, i followed the instructions to the letter. My working fix is just a monkey patch to bashrc. The tests are failing immediately after the clone.
The test/fast suite has far too many failures for me to confidently continue with the contribution.
Can you help me sort it out?
Operating system and version:
AlmaLinux 9
nvm debug output:
Details
nvm --version: v0.40.4
$SHELL: /bin/bash
$SHLVL: 1
whoami: 'user'
${HOME}: /home/user
${NVM_DIR}: '${HOME}/.nvm'
${PATH}: ${NVM_DIR}/versions/node/v20.20.0/bin:${HOME}/bin:${HOME}/.local/bin:${HOME}/.local/share/pnpm:/usr/share/Modules/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:${HOME}/go/bin:${HOME}/go/bin
$PREFIX: ''
${NPM_CONFIG_PREFIX}: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'GNU bash, version 5.1.8(1)-release (x86_64-redhat-linux-gnu)'
uname -a: 'Linux 5.14.0-611.13.1.el9_7.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Dec 11 04:57:59 EST 2025 x86_64 x86_64 x86_64 GNU/Linux'
checksum binary: 'sha256sum'
OS version: AlmaLinux 9.7 (Moss Jungle Cat)
awk: /usr/bin/awk, GNU Awk 5.1.0, API: 3.0 (GNU MPFR 4.1.0-p9, GNU MP 6.2.0)
curl: /usr/bin/curl, curl 7.76.1 (x86_64-redhat-linux-gnu) libcurl/7.76.1 OpenSSL/3.5.1 zlib/1.2.11 brotli/1.0.9 libidn2/2.3.0 libpsl/0.21.1 (+libidn2/2.3.0) libssh/0.10.4/openssl/zlib nghttp2/1.43.0
wget: /usr/bin/wget, GNU Wget 1.21.1 built on linux-gnu.
git: /usr/bin/git, git version 2.47.3
ls: cannot access 'alias'$'\n''/usr/bin/grep': No such file or directory
grep: alias grep='grep --color=auto'
/usr/bin/grep (grep --color=auto), grep (GNU grep) 3.6
sed: /usr/bin/sed, sed (GNU sed) 4.8
cut: /usr/bin/cut, cut (GNU coreutils) 8.32
basename: /usr/bin/basename, basename (GNU coreutils) 8.32
rm: /usr/bin/rm, rm (GNU coreutils) 8.32
mkdir: /usr/bin/mkdir, mkdir (GNU coreutils) 8.32
xargs: /usr/bin/xargs, xargs (GNU findutils) 4.8.0
nvm current: v20.20.0
which node: ${NVM_DIR}/versions/node/v20.20.0/bin/node
which iojs: /usr/bin/which: no iojs in (${NVM_DIR}/versions/node/v20.20.0/bin:${HOME}/bin:${HOME}/.local/bin:${HOME}/.local/share/pnpm:/usr/share/Modules/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:${HOME}/go/bin:${HOME}/go/bin)
which npm: ${NVM_DIR}/versions/node/v20.20.0/bin/npm
npm config get prefix: ${NVM_DIR}/versions/node/v20.20.0
npm root -g: ${NVM_DIR}/versions/node/v20.20.0/lib/node_modulesnvm ls output:
Details
v20.20.0
-> v25.6.0
default -> 25 (-> v25.6.0 *)
iojs -> N/A (default)
node -> stable (-> v25.6.0 *) (default)
stable -> 25.6 (-> v25.6.0 *) (default)
unstable -> N/A (default)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.12 (-> N/A)
lts/fermium -> v14.21.3 (-> N/A)
lts/gallium -> v16.20.2 (-> N/A)
lts/hydrogen -> v18.20.8 (-> N/A)
lts/iron -> v20.20.0 *
lts/jod -> v22.22.0 (-> N/A)
lts/krypton -> v24.13.0 (-> N/A)
lts/* -> lts/krypton (-> N/A)
How did you install nvm?
Instructions in readme
What steps did you perform?
clone repo, npm init, npm run test/fast (also tried make test).
What happened?
Dozens of test failures, many pertaining to lts versions.
What did you expect to happen?
Most of the tests would pass right out of the box.
Is there anything in any of your profile files that modifies the PATH?
Absolutely not (other than nvm!)
I have a PR that i'd like to submit but I can't get a valid dev setup to pass ALL of the tests (like over 100 do pass, but 37 fail...) right out of the box. My setup is not overly customized.
The PR addresses issues with default node version not being "sticky", there is an open issue for that. I got it fixed by directly patching the relevant files and thought I'd share the love.
Note: I have not altered the dev folder in any way, i followed the instructions to the letter. My working fix is just a monkey patch to bashrc. The tests are failing immediately after the clone.
The test/fast suite has far too many failures for me to confidently continue with the contribution.
Can you help me sort it out?
Operating system and version:
AlmaLinux 9
nvm debugoutput:Details
nvm lsoutput:Details
How did you install
nvm?Instructions in readme
What steps did you perform?
clone repo, npm init, npm run test/fast (also tried
make test).What happened?
Dozens of test failures, many pertaining to lts versions.
What did you expect to happen?
Most of the tests would pass right out of the box.
Is there anything in any of your profile files that modifies the
PATH?Absolutely not (other than nvm!)