Skip to content
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

Occasionally error: 1823 Segmentation fault (core dumped) npm install #1005

Open
3 tasks
aladdin-add opened this issue Apr 8, 2024 · 4 comments
Open
3 tasks
Assignees
Labels
bug Something isn't working

Comments

@aladdin-add
Copy link

aladdin-add commented Apr 8, 2024

Description:

Occasionally when running npm install:

Run npm install
/home/runner/work/_temp/9d355b[4](https://github.com/eslint/eslint/actions/runs/8598532822/job/23559533208?pr=18289#step:4:5)d-c108-413d-9445-84fc1608c1c2.sh: line 1:  1823 Segmentation fault      (core dumped) npm install
Error: Process completed with exit code 139.

Action version: actions/setup-node@v4
Specify the action version

Platform:

  • [x ] Ubuntu
  • macOS
  • Windows

Runner type:

  • [ x] Hosted
  • Self-hosted

Tools version: lts/* + npm

Repro steps:
https://github.com/eslint/eslint/actions/runs/8598532822/job/23559533208?pr=18289

Expected behavior:
install successfully.

Actual behavior:
as above.

@aladdin-add aladdin-add added bug Something isn't working needs triage labels Apr 8, 2024
@aladdin-add
Copy link
Author

@aparnajyothi-y
Copy link
Contributor

Hello @aladdin-add, Thank you for creating the issue and we will look into it :)

@gowridurgad gowridurgad self-assigned this Apr 26, 2024
@gowridurgad
Copy link

Hi @aladdin-add , We've successfully executed the workflow without encountering any errors. Here's the screenshot for your reference.
If you encounter the same error in future, below are some troubleshooting steps which might resolve this issue:

  1. Delete the node_modules directory and package-lock.json file, then run npm install again
- name: Install dependencies
    run: |
      rm -rf node_modules package-lock.json
      npm install
  1. Check whether there are any incompatible versions of packages in your package.json file.
  2. Ensure that Node.js is up-to-date
steps:
- name: Setup Node.js environment
  uses: actions/setup-node@v4
  with:
    node-version: '20' # or any latest stable version
Screenshot 2024-05-02 at 5 17 49 PM

@aladdin-add
Copy link
Author

Yes, it's not 100% reproduceable: it disappeared when I re-run it. Just filed it in case someone else encountered.

some more info:

  1. eslint was not using lockfile: https://github.com/eslint/eslint?tab=readme-ov-file#why-doesnt-eslint-lock-dependency-versions
  2. the failed job was already using node lts(20.x)

Please feel free to close if you think there is no concrete action here. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants