Node fails to install on macos

[circleci-public]

Node fails to install on macos

[KyleTryon]

Thank you for the report @MasterOdin. We will investigate.

[KyleTryon]

Hello @MasterOdin I have investigated the issue and I am not currently able to replicate it. I am currently working on a new branch and the tests are passing. I specifically tested out your config above, also passing.
https://app.circleci.com/pipelines/github/KyleTryon/CircleCI-Metadata-Build/135/workflows/c78577ab-e68c-4da4-8f4f-855bb59ad754/jobs/357

One difference, I see you have circleci/[email protected] listed but 4.1.1 does not yet exist so I used 4.1.0.

Please let me know if I have missed anything. We'll have a Node orb update coming soon but at the moment it wont contain any new features (yet).

[MasterOdin]

@KyleTryon Thanks for looking into this. The 4.1.1 was a typo on my part (as well as having the pipeline named build-macos in one spot and build in another as I trimmed down our production config to an example here.

I just re-tried this and I'm hitting the same failure from my OP. Looking at the build logs between the two look essentially the same (with a difference of a number of environment variables that should have no nvm effect) so I'm stumped.

Happy to provide a link to it via email or other means, though probably not directly posting here given it's a private project.

[KyleTryon]

Thanks @MasterOdin happy to take a look. Would you mind opening a support ticket and referencing this GitHub issue? The support team will reroute the information to me.

https://support.circleci.com/hc/en-us/requests/new

Once the issue is resolved we will respond there and comment what is appropriate here.

[KyleTryon]

@MasterOdin Thank you, I have taken a look. Would you mind pushing a new commit? I think what may have happened was a temporary network glitch, likely on the side of the nvm repo. My assumption is if you push again the issue will be resolved. Please let us know how it goes.

[KyleTryon]

Closing as the issue is not replicable or appears to be fixed. Please feel free to respond at any time to re-open this issue.

[MasterOdin]

I made another commit and it failed in the same way.

[KyleTryon]

@MasterOdin sorry to bother you for this again, but could I ask you to open a new ticket for this issue with the support team explicitly giving "ssh permission". If it would be alright with you, I would like to SSH into your build and one of mine simultaneously and run a few commands to try and figure out why we may not be able to replicate this.

Just to be extra clear, this will mean that we will SSH into your repository with access to code and the environment, though we would only be using our access to run NVM commands and attempt to resolve this issue. If that is acceptable, please open a ticket giving SSH permissions.

Thank you.

[MasterOdin]

Sorry for the delay on this, support ticket sent in.

[KyleTryon]

@MasterOdin We (cc @gmemstr) believe we may have discovered the issue.

Included in your repository is an .nvmrc specifying version 12.13.0, this is why in the output above in the error you have provided mentions that is attempting to use 12.13.0, though it has not been specified in the orb.

This is instructing NVM to use 12.13.0, while looking into this I discovered this project which highlights this issue in their usage example (there is not much out there I could find) https://github.com/nickstanish/nvm-shell-integration#usage

The general consensus online does appear to be that committing your .nvmrc file is generally encouraged, or at least should not be damaging.

We will be filing an issue with NVM and possibly a PR. It appears there are provided scripts for automatically installing and using the version in the .nvmrc file provided on the nvm repo, but we need this behavior present during the installation as the installer appears to use the version in the .nvmrc without first checking if it is installed.

For solutions in the meantime I would recommend either:

• Not committing the .nvmrc file
• Deleting the file in CircleCI prior to using the node install command (specifying the version in config).

Issue: nvm-sh/nvm#2430