GIthub Actions failed to run on Node 16 and Node 20

[khajatakreemulla]

Select Topic Area

Question

Body

Hello,

I'm encountering issues with my GitHub Actions workflow, specifically with the npm ci step failing.
We previously ran the environment on Node.js 16.x, but recently it started failing. As recommended by GitHub in this announcement, we attempted to update our workflow to use Node.js 20.x. Along with this, we also updated actions/checkout to v4 and actions/setup-node to v4.

Despite these changes, the npm ci step continues to fail for both Node.js 16.x and 20.x. Error: The operation was canceled.

This are my node 16 configurations

# This workflow will do a clean installation of node dependencies, cache/restore them, build the source code and run tests across different versions of node
# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs

name: npm test

on:
  workflow_dispatch:
  pull_request:
    branches: [ "main" ]

jobs:
  build:
    
    timeout-minutes: 5

    services:
      mongodb:
        image: mongo:6.0
        ports:
          - 27017:27017
      redis:
        image: redis:6.2
        ports:
          - 6379:6379

    strategy:
      matrix:
        node-version: [16.x]
        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
        os: [ubuntu-22.04]
    
    runs-on: ${{ matrix.os }}
    
    steps:
    - uses: actions/checkout@v3
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v3
      with:
        node-version: ${{ matrix.node-version }}
        cache: 'npm'
    - name: Install dependencies
      run: npm ci
    #- run: npm run build --if-present
    - name: Copy test configuration
      run: cp config/env/test.js_SAMPLE config/env/test.js
    - name: Run tests on ${{ matrix.os }} node ${{ matrix.node-version }}
      run: npm test

This are my current node 20 configurations as per this announcement

# This workflow will do a clean installation of node dependencies, cache/restore them, build the source code and run tests across different versions of node
# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs

name: npm test

on:
  workflow_dispatch:
  pull_request:
    branches: [ "main" ]

jobs:
  build:

    timeout-minutes: 5

    services:
      mongodb:
        image: mongo:6.0
        ports:
          - 27017:27017
      redis:
        image: redis:6.2
        ports:
          - 6379:6379

    strategy:
      matrix:
        node-version: [20.x]
        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
        os: [ubuntu-22.04]
    
    runs-on: ${{ matrix.os }}
    
    steps:
    - uses: actions/checkout@v4
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v4
      with:
        node-version: ${{ matrix.node-version }}
        cache: 'npm'
    - name: Install dependencies
      run: npm ci
    #- run: npm run build --if-present
    - name: Copy test configuration
      run: cp config/env/test.js_SAMPLE config/env/test.js
    - name: Run tests on ${{ matrix.os }} node ${{ matrix.node-version }}
      run: npm test

Has anyone experienced similar problems or have any suggestions for troubleshooting and resolving this issue?

Any help or insights would be greatly appreciated.

Thank you!

[IAreGitHub]

Same issues build for NextJS are failing due to npm ci issues

[ChristopherHX]

timeout-minutes: 5

I never set such a small timeout for real workflows.

Is npm ci really hanging or do you don't give it enough time?

a timeout of 10 or 15min would not be that strict.
My Actions jobs are not always as fast as they has been, once they got faster however slower is more likely to happen

[khajatakreemulla]

@nismolap @ChristopherHX i have been running the test for about 6 months with timeout of 5 mins only it was working fine all the time
The issues started for some time so i dont think any issue with timeout or using resources like mongodb and redis.

[ChristopherHX]

I'm only telling you that the symptom #[ERROR]The operation was canceled after ca. 5min comes from your job timeout setting of 5 minutes.

I took these info out of your screenshot.

Then my first step I would do is increasing the timeout.

The issues started for some time

I use GitHub Actions as well, but I always have to adjust the workflow or it stops working.

Regarding npm ci,
Here some examples that impact the time needed

• adding new packages (packages can run code on install)
• npm degraded availability
• GitHub Actions slow internet to npm
• updated packages

I'm using GitHub free, so I don't expect support for my part.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[khajatakreemulla]

Found the solution: One of the Node package had been unable to install due to which the process was stopping. removing the package fixed the action.