Skip to content

node-versions only packaging x64, include arm64 please #857

Closed

Description

@jpike88

I have arm runners and use an LTS version of node included in https://github.com/actions/node-versions/releases. But I use arm64, only x64 builds are in there.

Please include both architectures so I can leverage fast downloads.

Thanks

Activity

  1. changed the title [-]node-versions only packaging x64, include arm please[/-] [+]node-versions only packaging x64, include arm64 please[/+] on Sep 20, 2023
  2. nikolai-laevskii commented on Sep 21, 2023

    @nikolai-laevskii
    Contributor

    Thanks for creating an issue! We will look into and come back to you with the details!

  3. bennet-agital commented on Sep 21, 2023

    @bennet-agital

    Currently experiencing this:

    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?

  4. jpike88 commented on Sep 22, 2023

    @jpike88
    Author

    Much appreciated. As you can see it's a very annoying wait!

    Screenshot 2023-09-22 at 14 59 12
  5. jpike88 commented on Sep 27, 2023

    @jpike88
    Author

    this issue is quite acute. is there an official workaround for this (maybe I can cache the binary myself), while still leveraging this step?

  6. dustin-engstrom commented on Oct 17, 2023

    @dustin-engstrom

    I think we have to wait for this issue to be addressed.

    actions/runner-images#5631

  7. jpike88 commented on Oct 18, 2023

    @jpike88
    Author

    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.

  8. dustin-engstrom commented on Oct 18, 2023

    @dustin-engstrom

    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.

  9. v-aparnajyothi-y commented on Mar 28, 2024

    @v-aparnajyothi-y
    Contributor

    fix merged and arm64 packages supporting for linux and windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

feature requestNew feature or request to improve the current logicneeds eyes

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions