-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Occasional flake when setting up node #116
Comments
Hi @mockdeep ! Thanks for submitting this issue. Can you inform us on how often this occurs? I believe this might be an issue with the install script provided by nvm, or with github being flaky on clone connections. While searching around for issues like this, I kept stumbling across posts where people are changing the port from ssh to ssl: https://gist.github.com/kcc0/d88150ace547976cfcccd578f30c816a However, I think that might be a solution to when the 22 port is blocked by a firewall, which doesn't apply here. |
Hi @Jaryt, thanks for the quick response. We see this issue a handful of times each week. I think it's probably our largest source of flake in our test suite at the moment. Out of curiosity, I was looking at how asdf installs node and it looks like they use Also, should the installation be cached so that it doesn't need to be reinstalled each time? I wonder if that might reduce the flake some, too. |
I'd have to investigate the caching of .nvm further to ensure that it's stable. But since you are encountering this, I would encourage you to experiment with caching |
This is failing pretty hard for us right now. I haven't had a chance to try the caching, yet, but we're seeing a ton of failures with exit status 18. It's hard to tell anything else about why it is failing from the output: output
|
Moving to backlog as we will be escalating this to our images team. |
Orb version:
5.0.0
What happened:
We occasionally see flaky builds where node or NPM fails to install. For example, here's the output from one recent failure:
failure output
Expected behavior:
Node should reliably install in the container.
The text was updated successfully, but these errors were encountered: