You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
node-versions only packaging x64, include arm64 please #857
changed the title [-]node-versions only packaging x64, include arm please[/-][+]node-versions only packaging x64, include arm64 please[/+]on Sep 20, 2023
Attempting to download 18...
Not found in manifest. Falling back to download directly from Node
Acquiring 18.18.0 - arm64 from https://nodejs.org/dist/v18.18.0/node-v18.18.0-linux-arm64.tar.gz
aborted
Waiting 18 seconds before trying again
could be resolved by including arm versions directly?
Why wait for that?? Buildjet has offered arm64 runners for quite some time now, it’s those runners that I’m using. Not sure why waiting for github to catch up is necessary here.
Why wait for that?? Buildjet has offered arm64 runners for quite some time now, it’s those runners that I’m using. Not sure why waiting for github to catch up is necessary here.
My comment is based on the way this setup-node action currently works. If you look here you'll see that it pulls a manifest file of current node-versions from this file in a separate repo. But that file does not currently contain any arm64 targets; which is why the action always ends up downloading directly from Node instead. The issue I linked in my comment is a request to add arm64 targets to that manifest file in the other repo.
Feel free to propose other workarounds though. I just thought it would be helpful to know that there's an issue raised already at the source of this problem.
Activity
[-]node-versions only packaging x64, include arm please[/-][+]node-versions only packaging x64, include arm64 please[/+]nikolai-laevskii commentedon Sep 21, 2023
Thanks for creating an issue! We will look into and come back to you with the details!
bennet-agital commentedon Sep 21, 2023
Currently experiencing this:
could be resolved by including arm versions directly?
jpike88 commentedon Sep 22, 2023
Much appreciated. As you can see it's a very annoying wait!
jpike88 commentedon Sep 27, 2023
this issue is quite acute. is there an official workaround for this (maybe I can cache the binary myself), while still leveraging this step?
dustin-engstrom commentedon Oct 17, 2023
I think we have to wait for this issue to be addressed.
actions/runner-images#5631
jpike88 commentedon Oct 18, 2023
Why wait for that?? Buildjet has offered arm64 runners for quite some time now, it’s those runners that I’m using. Not sure why waiting for github to catch up is necessary here.
dustin-engstrom commentedon Oct 18, 2023
My comment is based on the way this
setup-nodeaction currently works. If you look here you'll see that it pulls a manifest file of current node-versions from this file in a separate repo. But that file does not currently contain any arm64 targets; which is why the action always ends up downloading directly from Node instead. The issue I linked in my comment is a request to add arm64 targets to that manifest file in the other repo.Feel free to propose other workarounds though. I just thought it would be helpful to know that there's an issue raised already at the source of this problem.
v-aparnajyothi-y commentedon Mar 28, 2024
fix merged and arm64 packages supporting for linux and windows.