question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] Using any architecture other than x64 fails to run

See original GitHub issue

Here’s my yaml file:

name: Test

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

jobs:
  auto-test:
    runs-on: ${{ matrix.os }}

    strategy:
      matrix:
        os:
          - ubuntu-latest
          - macos-latest
          - windows-latest
        node-version:
          - 14
          - 16
          - 17
        architecture:
          - x64
          - arm64
    steps:
    - run: git config --global core.autocrlf false  # Mainly for Windows
    - uses: actions/checkout@v2

    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v2
      with:
        node-version: ${{ matrix.node-version }}
        architecture: ${{ matrix.architecture }}

    - name: Get npm cache directory
      id: npm-cache-dir
      run: |
        echo "::set-output name=dir::$(npm config get cache)"
    - uses: actions/cache@v3
      id: npm-cache # use this to check for `cache-hit` ==> if: steps.npm-cache.outputs.cache-hit != 'true'
      with:
        path: ${{ steps.npm-cache-dir.outputs.dir }}
        key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
        restore-keys: |
          ${{ runner.os }}-node-

    - run: npm run install

Error happens when running Get npm cache directory with the following:

Run echo "::set-output name=dir::$(npm config get cache)"
  echo "::set-output name=dir::$(npm config get cache)"
  shell: /usr/bin/bash -e {0}
/opt/hostedtoolcache/node/14.19.1/arm64/bin/node: 1: ELF�8%�@��n@8: not found
check_suite_focus=true#step:5:2): Syntax error: ")" unexpected

My understanding is that even though setup-node is using an ARM64 release, the runner itself from Github is using a different architecture?

I don’t think this is related with setup-node but should be documented. The advanced examples make it look as if just adding arm64 is going to make your CI run just fine, which is not the case.

Is there a Github Action solution for this?

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
panticmiloscommented, Apr 14, 2022

Hi @gaby,

We will investigate this issue further.

0reactions
gabycommented, Apr 15, 2022

@panticmilos ideally the documentation for setup-node is updated to indicate that only x64 works on Github Hosted runners, for anything else Self-Hosted runners are needed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Xcode 12 beta 4 - error compiling … | Apple Developer Forums
But when i run the same code base with xcode 11.3.1 then it works fine for me . Right now i am unable...
Read more >
Bug: Platform architecture does not report bitness correctly
Hello, Platform architecture reports x86 even when its running in 64bit (compiled with VS for anyCPU and running on a 64bit machine)
Read more >
.net - How do I fix the Visual Studio compile error, "mismatch ...
First, it really is just a warning. It should not hurt anything if you are just dealing with x86 dependencies. Microsoft is just...
Read more >
221969 – [launcher] Eclipse unable to determine architecture ...
Obviously, that situation does not apply here; running either a 32 bit VM or a 64 bit Eclipse will solve your problem. I...
Read more >
Support 64-bit architectures - Android Developers
Your app makes use of native code if it: Uses any C/C++ (native) code in your app. Links with any third party native...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found