-
Notifications
You must be signed in to change notification settings - Fork 46
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
GitHub Actions failing at installation of Node.js #309
GitHub Actions failing at installation of Node.js #309
Comments
Test run on main branch fails too. Latest release of ubuntu-22.04 bumped nvm to 0.40.0. Looks to me as related nvm-sh/nvm#3405. |
Maybe |
Coincidentally I arrived to this issue, worth checking it. It seems that some incompatibility between nvm (that we use to install the target nodejs version) and GitHub actions may be the root of the problem: nvm-sh/nvm#3405 A fix is being worked on, based on the last comments there… |
Ah, @kabalin , just saw your comment now! Snap! |
Yeah, runner-images would need to be updated too following the fix in nvm, will take time. Temporary workaround is to install nvm 0.39.7 explicitly like at #310. |
…we swap to temporary workaround (moodlehq/moodle-plugin-ci#310)
Solved mine temporarily by adding the following before
Just a temporary fix before this plugin is updated |
So, you are installing version 20 explicitly, can you share the workflow? I would expect install step to fail as it only bypass node installation if The easiest workaround for now is described in #310, a one-liner fix to downgrade nvm. |
workaround for moodlehq/moodle-plugin-ci#309
|
Hmm, does not seem have effect (unless I am using it wrong way) |
You're using it correctly afaict (altho |
This is a temporary fix and if this is fixed upstream we should consider reverting this.
This is a temporary fix and if this is fixed upstream we should consider reverting this.
This is a temporary fix and if this is fixed upstream we should consider reverting this.
This is a temporary fix and if this is fixed upstream we should consider reverting this.
Install 0.39.7 explicitly as part of vendor installation, so we have control over the version we use. For cases where nvm is not required (pre-installed in the image, use --no-nvm param for install command) Fixes moodlehq#309
Install 0.39.7 explicitly as part of vendor installation, so we have control over the version we use. For cases where nvm is not required (pre-installed in the image, use --no-nvm param for install command) Fixes moodlehq#309
Install 0.39.7 explicitly as part of vendor installation, so we have control over the version we use. For cases where nvm is not required (pre-installed in the image, use --no-nvm param for install command) Fixes moodlehq#309
Install 0.39.7 explicitly as part of vendor installation, so we have control over the version we use. For cases where nvm is not required (pre-installed in the image, use --no-nvm param for install command) Fixes moodlehq#309
We fixed this in 4.5.4 release, those who added temporary workaround can safely remove it. Sorry for delaying the fix and thanks for your patience :) |
@kabalin Thank you so much! Can a similar fix be applied to the 3.x branch? We still do some testing against older versions which do not work with 4.x |
Remove workaround for moodlehq/moodle-plugin-ci#309
We should not rely on success exit status from nvm.sh loading. Fixes moodlehq#309
fwiw v0.40.1 of nvm has been released, which should fix this issue. |
A few days ago, some of my CI checks randomly failed at the
install moodle-plugin-ci
step. After a few retries, all checks finally passed. In the meantime, things have become worse. Currently, all checks are constantly failing. Some other developers reported the same in the dev chat.The text was updated successfully, but these errors were encountered: