starred/act
1
0
Fork 0
mirror of https://github.com/nektos/act.git synced 2026-04-26 01:15:51 +03:00
Code Issues 289 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #2194] Slow running with timeouts #1036

New issue
Closed
opened 2026-03-01 21:48:23 +03:00 by kerem · 4 comments
kerem commented 2026-03-01 21:48:23 +03:00
Owner
Copy link

Originally created by @fabiobsantosprogrow on GitHub (Feb 1, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2194

Bug report info

act version:            0.2.57
GOOS:                   linux
GOARCH:                 amd64
NumCPU:                 12
Docker host:            DOCKER_HOST environment variable is not set
Sockets found:
        /var/run/docker.sock
Config files:           
        /home/progrow/.actrc:
                #-P ubuntu-latest=nektos/act-environments-ubuntu:22.04
                -P ubuntu-latest=catthehacker/ubuntu:full-latest
                -P ubuntu-22.04=catthehacker/ubuntu:full-22.04
                -P ubuntu-20.04=catthehacker/ubuntu:full-20.04
                -P ubuntu-18.04=catthehacker/ubuntu:full-18.04
                --artifact-server-path /home/progrow/act
                --pull=false
Build info:
        Go version:            go1.21.5
        Module path:           command-line-arguments
        Main version:          
        Main path:             
        Main checksum:         
        Build settings:
                -buildmode:           exe
                -compiler:            gc
                -ldflags:             -X main.version=0.2.57
                DefaultGODEBUG:       panicnil=1
                CGO_ENABLED:          1
                CGO_CFLAGS:           
                CGO_CPPFLAGS:         
                CGO_CXXFLAGS:         
                CGO_LDFLAGS:          
                GOARCH:               amd64
                GOOS:                 linux
                GOAMD64:              v1
Docker Engine:
        Engine version:        20.10.23
        Engine runtime:        runc
        Cgroup version:        1
        Cgroup driver:         cgroupfs
        Storage driver:        overlay2
        Registry URI:          https://index.docker.io/v1/
        OS:                    Ubuntu 20.04.3 LTS
        OS type:               linux
        OS version:            20.04
        OS arch:               x86_64
        OS kernel:             5.15.0-92-generic
        OS CPU:                12
        OS memory:             15854 MB
        Security options:
                name=apparmor
                name=seccomp,profile=default

Command used with act

act -j integration_test_stage -W .github/workflows/ci-pipeline.yml

Describe issue

Slow running pipeline...
Sometimes getting timeout erros like this: Error: Get "https://github.com/actions/setup-node/info/refs?service=git-upload-pack": dial tcp 140.82.121.3:443: i/o timeout

Kind regards

Link to GitHub repository

No response

Workflow content

name: ci-pipeline
permissions: write-all

#new comment
on:
  push:
    branches: [develop]
    #branches: [develop, 'release/**']
  release:
    types: [created]

env:
  DB_CONNECTIONSTRING: postgresql://postgres:%23progrow%3D2015!@localhost:5432/
  DB_SCHEMA: test_db
  LOG_LEVEL: error
  DISABLE_JOB_SALVAGING: true
  NUMBER_OF_PROCESSING_THREADS: 16
  NUMBER_RETRIES_PER_JOB: 5
  DB_ENABLE_PATCHER: false
  REDIS_PORT: 6380
  VIEWS_TTL_START: 15
  EXPRESS_PORT: 3001
  PATCHER_APP_ENABLE: false
  REDIS_URI_INTEGRATION: redis://localhost:6380/0
  REDIS_URI_PRODUCT: redis://localhost:6380/1
  DISABLE_AUTH: true

jobs:
  commit_stage:
    name: Commit Stage
    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [20.x]

    steps:
      - uses: actions/checkout@v3
      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v3
        with:
          node-version: ${{ matrix.node-version }}

      - name: Build
        run: npm install && npx lerna run build

      - name: Unit test
        run: npx lerna run test -- unit

      - name: Archive artifacts
        uses: actions/upload-artifact@v3
        with:
          name: development-pipeline-etl-core
          path: |
            packages/**/dist
            !packages/**/dist/*.md
          retention-days: 7

  integration_test_stage:
    name: Integration test stage
    needs: commit_stage
    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [20.x]

    steps:
      - uses: actions/checkout@v3
      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v3
        with:
          node-version: ${{ matrix.node-version }}

      - name: Download artifacts
        uses: actions/download-artifact@v3
        with:
          name: development-pipeline-etl-core
          path: ./packages

      - name: Install necessary dependencies
        run: npm install

      - name: Sets up environment
        run: |
          sudo docker-compose up -d
          cd packages/management && npm run start &

      - name: Integration test stage
        run: cd packages/core && npm run test -- integration

Relevant log output

Info on start:
INFO[0000] Start server on http://192.168.1.184:34567   
[ci-pipeline/Commit Stage] 🚀  Start image=catthehacker/ubuntu:full-latest
INFO[0000] Parallel tasks (0) below minimum, setting to 1 
[ci-pipeline/Commit Stage]   🐳  docker pull image=catthehacker/ubuntu:full-latest platform= username= forcePull=false
INFO[0000] Parallel tasks (0) below minimum, setting to 1 
Sometimes get timeout communication:
[ci-pipeline/Integration test stage] 🚀  Start image=catthehacker/ubuntu:full-latest
INFO[0054] Parallel tasks (0) below minimum, setting to 1 
[ci-pipeline/Integration test stage]   🐳  docker pull image=catthehacker/ubuntu:full-latest platform= username= forcePull=false
INFO[0054] Parallel tasks (0) below minimum, setting to 1 
[ci-pipeline/Integration test stage]   🐳  docker create image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host"
[ci-pipeline/Integration test stage]   🐳  docker run image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host"
[ci-pipeline/Integration test stage]   🐳  docker exec cmd=[chown -R 1001:127 /home/progrow/GitRepositories/DevOps/ETLCItest] user=0 workdir=
[ci-pipeline/Integration test stage]   ☁  git clone 'https://github.com/actions/setup-node' # ref=v3
[ci-pipeline/Integration test stage] Cleaning up container for job Integration test stage
[ci-pipeline/Integration test stage] 🏁  Job succeeded
Error: Get "https://github.com/actions/setup-node/info/refs?service=git-upload-pack": dial tcp 140.82.121.3:443: i/o timeout

Additional information

No response

Originally created by @fabiobsantosprogrow on GitHub (Feb 1, 2024). Original GitHub issue: https://github.com/nektos/act/issues/2194 ### Bug report info ```plain text act version: 0.2.57 GOOS: linux GOARCH: amd64 NumCPU: 12 Docker host: DOCKER_HOST environment variable is not set Sockets found: /var/run/docker.sock Config files: /home/progrow/.actrc: #-P ubuntu-latest=nektos/act-environments-ubuntu:22.04 -P ubuntu-latest=catthehacker/ubuntu:full-latest -P ubuntu-22.04=catthehacker/ubuntu:full-22.04 -P ubuntu-20.04=catthehacker/ubuntu:full-20.04 -P ubuntu-18.04=catthehacker/ubuntu:full-18.04 --artifact-server-path /home/progrow/act --pull=false Build info: Go version: go1.21.5 Module path: command-line-arguments Main version: Main path: Main checksum: Build settings: -buildmode: exe -compiler: gc -ldflags: -X main.version=0.2.57 DefaultGODEBUG: panicnil=1 CGO_ENABLED: 1 CGO_CFLAGS: CGO_CPPFLAGS: CGO_CXXFLAGS: CGO_LDFLAGS: GOARCH: amd64 GOOS: linux GOAMD64: v1 Docker Engine: Engine version: 20.10.23 Engine runtime: runc Cgroup version: 1 Cgroup driver: cgroupfs Storage driver: overlay2 Registry URI: https://index.docker.io/v1/ OS: Ubuntu 20.04.3 LTS OS type: linux OS version: 20.04 OS arch: x86_64 OS kernel: 5.15.0-92-generic OS CPU: 12 OS memory: 15854 MB Security options: name=apparmor name=seccomp,profile=default ``` ### Command used with act ```sh act -j integration_test_stage -W .github/workflows/ci-pipeline.yml ``` ### Describe issue Slow running pipeline... Sometimes getting timeout erros like this: Error: Get "https://github.com/actions/setup-node/info/refs?service=git-upload-pack": dial tcp 140.82.121.3:443: i/o timeout Kind regards ### Link to GitHub repository _No response_ ### Workflow content ```yml name: ci-pipeline permissions: write-all #new comment on: push: branches: [develop] #branches: [develop, 'release/**'] release: types: [created] env: DB_CONNECTIONSTRING: postgresql://postgres:%23progrow%3D2015!@localhost:5432/ DB_SCHEMA: test_db LOG_LEVEL: error DISABLE_JOB_SALVAGING: true NUMBER_OF_PROCESSING_THREADS: 16 NUMBER_RETRIES_PER_JOB: 5 DB_ENABLE_PATCHER: false REDIS_PORT: 6380 VIEWS_TTL_START: 15 EXPRESS_PORT: 3001 PATCHER_APP_ENABLE: false REDIS_URI_INTEGRATION: redis://localhost:6380/0 REDIS_URI_PRODUCT: redis://localhost:6380/1 DISABLE_AUTH: true jobs: commit_stage: name: Commit Stage runs-on: ubuntu-latest strategy: matrix: node-version: [20.x] steps: - uses: actions/checkout@v3 - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@v3 with: node-version: ${{ matrix.node-version }} - name: Build run: npm install && npx lerna run build - name: Unit test run: npx lerna run test -- unit - name: Archive artifacts uses: actions/upload-artifact@v3 with: name: development-pipeline-etl-core path: | packages/**/dist !packages/**/dist/*.md retention-days: 7 integration_test_stage: name: Integration test stage needs: commit_stage runs-on: ubuntu-latest strategy: matrix: node-version: [20.x] steps: - uses: actions/checkout@v3 - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@v3 with: node-version: ${{ matrix.node-version }} - name: Download artifacts uses: actions/download-artifact@v3 with: name: development-pipeline-etl-core path: ./packages - name: Install necessary dependencies run: npm install - name: Sets up environment run: | sudo docker-compose up -d cd packages/management && npm run start & - name: Integration test stage run: cd packages/core && npm run test -- integration ``` ### Relevant log output ```sh Info on start: INFO[0000] Start server on http://192.168.1.184:34567 [ci-pipeline/Commit Stage] 🚀 Start image=catthehacker/ubuntu:full-latest INFO[0000] Parallel tasks (0) below minimum, setting to 1 [ci-pipeline/Commit Stage] 🐳 docker pull image=catthehacker/ubuntu:full-latest platform= username= forcePull=false INFO[0000] Parallel tasks (0) below minimum, setting to 1 Sometimes get timeout communication: [ci-pipeline/Integration test stage] 🚀 Start image=catthehacker/ubuntu:full-latest INFO[0054] Parallel tasks (0) below minimum, setting to 1 [ci-pipeline/Integration test stage] 🐳 docker pull image=catthehacker/ubuntu:full-latest platform= username= forcePull=false INFO[0054] Parallel tasks (0) below minimum, setting to 1 [ci-pipeline/Integration test stage] 🐳 docker create image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host" [ci-pipeline/Integration test stage] 🐳 docker run image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host" [ci-pipeline/Integration test stage] 🐳 docker exec cmd=[chown -R 1001:127 /home/progrow/GitRepositories/DevOps/ETLCItest] user=0 workdir= [ci-pipeline/Integration test stage] ☁ git clone 'https://github.com/actions/setup-node' # ref=v3 [ci-pipeline/Integration test stage] Cleaning up container for job Integration test stage [ci-pipeline/Integration test stage] 🏁 Job succeeded Error: Get "https://github.com/actions/setup-node/info/refs?service=git-upload-pack": dial tcp 140.82.121.3:443: i/o timeout ``` ### Additional information _No response_
kerem 2026-03-01 21:48:23 +03:00
kerem commented 2026-03-01 21:48:24 +03:00
Author
Owner
Copy link

@ChristopherHX commented on GitHub (Feb 1, 2024):

The current default old action cache does a full clone, while it isn't required. And is sometimes ultra slow.

Note: The following requires you to update act v0.2.58.

@fabiobsantosprogrow Can you please try act -j integration_test_stage -W .github/workflows/ci-pipeline.yml --use-new-action-cache to see if it still timeouts frequently. (Download less data from git)

Alternatively the offline mode could help you by stop fetching updates if you just want to test with the current version of all actions and images act -j integration_test_stage -W .github/workflows/ci-pipeline.yml --action-offline-mode

<!-- gh-comment-id:1921734148 --> @ChristopherHX commented on GitHub (Feb 1, 2024): The current default **old** action cache does a full clone, while it isn't required. And is sometimes ultra slow. Note: The following requires you to update act v0.2.58. @fabiobsantosprogrow Can you please try `act -j integration_test_stage -W .github/workflows/ci-pipeline.yml --use-new-action-cache` to see if it still timeouts frequently. (Download less data from git) Alternatively the offline mode could help you by stop fetching updates if you just want to test with the current version of all actions and images `act -j integration_test_stage -W .github/workflows/ci-pipeline.yml --action-offline-mode`
kerem commented 2026-03-01 21:48:24 +03:00
Author
Owner
Copy link

@fabiobsantosprogrow commented on GitHub (Feb 2, 2024):

I upgrade to act version 0.2.59.
Using the option --use-new-action-cache I'm getting this error:
INFO[0000] Start server on http://10.33.2.172:34567
[ci-pipeline/Commit Stage] 🚀 Start image=catthehacker/ubuntu:full-latest
INFO[0000] Parallel tasks (0) below minimum, setting to 1
[ci-pipeline/Commit Stage] 🐳 docker pull image=catthehacker/ubuntu:full-latest platform= username= forcePull=false
INFO[0000] Parallel tasks (0) below minimum, setting to 1
[ci-pipeline/Commit Stage] 🐳 docker create image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host"
[ci-pipeline/Commit Stage] 🐳 docker run image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host"
[ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /home/progrow/GitRepositories/DevOps/ETLCItest] user=0 workdir=
[ci-pipeline/Commit Stage] 🧪 Matrix: map[node-version:20.x]
[ci-pipeline/Commit Stage] ⭐ Run Main actions/checkout@v3
[ci-pipeline/Commit Stage] 🐳 docker cp src=/home/progrow/GitRepositories/DevOps/ETLCItest/. dst=/home/progrow/GitRepositories/DevOps/ETLCItest
[ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /home/progrow/GitRepositories/DevOps/ETLCItest] user=0 workdir=
[ci-pipeline/Commit Stage] ✅ Success - Main actions/checkout@v3
[ci-pipeline/Commit Stage] ⭐ Run Main Use Node.js 20.x
[ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /var/run/act/actions/actions-setup-node@v3/] user=0 workdir=
[ci-pipeline/Commit Stage] 🐳 docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir=
| node:internal/modules/cjs/loader:1137
| throw err;
| ^
|
| Error: Cannot find module '/var/run/act/actions/actions-setup-node@v3/dist/setup/index.js'
| at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
| at Module._load (node:internal/modules/cjs/loader:975:27)
| at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
| at node:internal/main/run_main_module:28:49 {
| code: 'MODULE_NOT_FOUND',
| requireStack: []
| }
|
| Node.js v18.19.0
[ci-pipeline/Commit Stage] ❌ Failure - Main Use Node.js 20.x
[ci-pipeline/Commit Stage] exitcode '1': failure
[ci-pipeline/Commit Stage] 🏁 Job failed
Error: Job 'Commit Stage' failed
progrow@progrow-IdeaPad-Creator-5-15IMH05:~/GitRepositories/DevOps/ETLCItest$ act -j integration_test_stage -W .github/workflows/ci-pipeline.yml
INFO[0000] Start server on http://10.33.2.172:34567
[ci-pipeline/Commit Stage] 🚀 Start image=catthehacker/ubuntu:full-latest
INFO[0000] Parallel tasks (0) below minimum, setting to 1
[ci-pipeline/Commit Stage] 🐳 docker pull image=catthehacker/ubuntu:full-latest platform= username= forcePull=false
INFO[0000] Parallel tasks (0) below minimum, setting to 1
[ci-pipeline/Commit Stage] 🐳 docker create image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host"
[ci-pipeline/Commit Stage] 🐳 docker run image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host"
[ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /home/progrow/GitRepositories/DevOps/ETLCItest] user=0 workdir=
[ci-pipeline/Commit Stage] 🧪 Matrix: map[node-version:20.x]
[ci-pipeline/Commit Stage] ⭐ Run Main actions/checkout@v3
[ci-pipeline/Commit Stage] 🐳 docker cp src=/home/progrow/GitRepositories/DevOps/ETLCItest/. dst=/home/progrow/GitRepositories/DevOps/ETLCItest
[ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /home/progrow/GitRepositories/DevOps/ETLCItest] user=0 workdir=
[ci-pipeline/Commit Stage] ✅ Success - Main actions/checkout@v3
[ci-pipeline/Commit Stage] ⭐ Run Main Use Node.js 20.x
[ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /var/run/act/actions/actions-setup-node@v3/] user=0 workdir=
[ci-pipeline/Commit Stage] 🐳 docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir=
| node:internal/modules/cjs/loader:1137
| throw err;
| ^
|
| Error: Cannot find module '/var/run/act/actions/actions-setup-node@v3/dist/setup/index.js'
| at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
| at Module._load (node:internal/modules/cjs/loader:975:27)
| at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
| at node:internal/main/run_main_module:28:49 {
| code: 'MODULE_NOT_FOUND',
| requireStack: []
| }
|
| Node.js v18.19.0
[ci-pipeline/Commit Stage] ❌ Failure - Main Use Node.js 20.x
[ci-pipeline/Commit Stage] exitcode '1': failure
[ci-pipeline/Commit Stage] 🏁 Job failed
Error: Job 'Commit Stage' failed

Using the option --action-offline-mode the job succeeded without timeout.
I try second time with --use-new-action-cache after running without the two options and get the same error.
If this option not works I will use the --action-offline-mode to increase speed and reduce timeouts.
Other question is about this message at the start of the job:
INFO[0000] Parallel tasks (0) below minimum, setting to 1
Changing the value of this parameter will increase the performance?

<!-- gh-comment-id:1923434474 --> @fabiobsantosprogrow commented on GitHub (Feb 2, 2024): I upgrade to act version 0.2.59. Using the option --use-new-action-cache I'm getting this error: INFO[0000] Start server on http://10.33.2.172:34567 [ci-pipeline/Commit Stage] 🚀 Start image=catthehacker/ubuntu:full-latest INFO[0000] Parallel tasks (0) below minimum, setting to 1 [ci-pipeline/Commit Stage] 🐳 docker pull image=catthehacker/ubuntu:full-latest platform= username= forcePull=false INFO[0000] Parallel tasks (0) below minimum, setting to 1 [ci-pipeline/Commit Stage] 🐳 docker create image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host" [ci-pipeline/Commit Stage] 🐳 docker run image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host" [ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /home/progrow/GitRepositories/DevOps/ETLCItest] user=0 workdir= [ci-pipeline/Commit Stage] 🧪 Matrix: map[node-version:20.x] [ci-pipeline/Commit Stage] ⭐ Run Main actions/checkout@v3 [ci-pipeline/Commit Stage] 🐳 docker cp src=/home/progrow/GitRepositories/DevOps/ETLCItest/. dst=/home/progrow/GitRepositories/DevOps/ETLCItest [ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /home/progrow/GitRepositories/DevOps/ETLCItest] user=0 workdir= [ci-pipeline/Commit Stage] ✅ Success - Main actions/checkout@v3 [ci-pipeline/Commit Stage] ⭐ Run Main Use Node.js 20.x [ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /var/run/act/actions/actions-setup-node@v3/] user=0 workdir= [ci-pipeline/Commit Stage] 🐳 docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir= | node:internal/modules/cjs/loader:1137 | throw err; | ^ | | Error: Cannot find module '/var/run/act/actions/actions-setup-node@v3/dist/setup/index.js' | at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15) | at Module._load (node:internal/modules/cjs/loader:975:27) | at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) | at node:internal/main/run_main_module:28:49 { | code: 'MODULE_NOT_FOUND', | requireStack: [] | } | | Node.js v18.19.0 [ci-pipeline/Commit Stage] ❌ Failure - Main Use Node.js 20.x [ci-pipeline/Commit Stage] exitcode '1': failure [ci-pipeline/Commit Stage] 🏁 Job failed Error: Job 'Commit Stage' failed progrow@progrow-IdeaPad-Creator-5-15IMH05:~/GitRepositories/DevOps/ETLCItest$ act -j integration_test_stage -W .github/workflows/ci-pipeline.yml INFO[0000] Start server on http://10.33.2.172:34567 [ci-pipeline/Commit Stage] 🚀 Start image=catthehacker/ubuntu:full-latest INFO[0000] Parallel tasks (0) below minimum, setting to 1 [ci-pipeline/Commit Stage] 🐳 docker pull image=catthehacker/ubuntu:full-latest platform= username= forcePull=false INFO[0000] Parallel tasks (0) below minimum, setting to 1 [ci-pipeline/Commit Stage] 🐳 docker create image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host" [ci-pipeline/Commit Stage] 🐳 docker run image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host" [ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /home/progrow/GitRepositories/DevOps/ETLCItest] user=0 workdir= [ci-pipeline/Commit Stage] 🧪 Matrix: map[node-version:20.x] [ci-pipeline/Commit Stage] ⭐ Run Main actions/checkout@v3 [ci-pipeline/Commit Stage] 🐳 docker cp src=/home/progrow/GitRepositories/DevOps/ETLCItest/. dst=/home/progrow/GitRepositories/DevOps/ETLCItest [ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /home/progrow/GitRepositories/DevOps/ETLCItest] user=0 workdir= [ci-pipeline/Commit Stage] ✅ Success - Main actions/checkout@v3 [ci-pipeline/Commit Stage] ⭐ Run Main Use Node.js 20.x [ci-pipeline/Commit Stage] 🐳 docker exec cmd=[chown -R 1001:127 /var/run/act/actions/actions-setup-node@v3/] user=0 workdir= [ci-pipeline/Commit Stage] 🐳 docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir= | node:internal/modules/cjs/loader:1137 | throw err; | ^ | | Error: Cannot find module '/var/run/act/actions/actions-setup-node@v3/dist/setup/index.js' | at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15) | at Module._load (node:internal/modules/cjs/loader:975:27) | at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) | at node:internal/main/run_main_module:28:49 { | code: 'MODULE_NOT_FOUND', | requireStack: [] | } | | Node.js v18.19.0 [ci-pipeline/Commit Stage] ❌ Failure - Main Use Node.js 20.x [ci-pipeline/Commit Stage] exitcode '1': failure [ci-pipeline/Commit Stage] 🏁 Job failed Error: Job 'Commit Stage' failed Using the option --action-offline-mode the job succeeded without timeout. I try second time with --use-new-action-cache after running without the two options and get the same error. If this option not works I will use the --action-offline-mode to increase speed and reduce timeouts. Other question is about this message at the start of the job: INFO[0000] Parallel tasks (0) below minimum, setting to 1 Changing the value of this parameter will increase the performance?
kerem commented 2026-03-01 21:48:24 +03:00
Author
Owner
Copy link

@ChristopherHX commented on GitHub (Feb 2, 2024):

Using the option --use-new-action-cache I'm getting this error

I forget that full images use a non root user, I have already noticed that bug https://github.com/nektos/act/issues/2183.

Yes keep using --action-offline-mode for now, the fastest possible way to execute act.

If you need that actions/images get updated, just skip using the offline mode once in a while.

PS:
create a .actrc in your cwd with content

--action-offline-mode

Then you can skip that flag, while running act and it will be applied automatically

<!-- gh-comment-id:1923646828 --> @ChristopherHX commented on GitHub (Feb 2, 2024): > Using the option --use-new-action-cache I'm getting this error I forget that full images use a non root user, I have already noticed that bug https://github.com/nektos/act/issues/2183. Yes keep using `--action-offline-mode` for now, the fastest possible way to execute act. If you need that actions/images get updated, just skip using the offline mode once in a while. PS: create a `.actrc` in your cwd with content ``` --action-offline-mode ``` Then you can skip that flag, while running act and it will be applied automatically
kerem commented 2026-03-01 21:48:24 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Aug 1, 2024):

Issue is stale and will be closed in 14 days unless there is new activity

<!-- gh-comment-id:2261693754 --> @github-actions[bot] commented on GitHub (Aug 1, 2024): Issue is stale and will be closed in 14 days unless there is new activity
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
dependabot/go_modules/github.com/go-git/go-git/v5-5.18.0
dependabot/go_modules/dependencies-08815e2262
mergify/configuration-deprecated-update
dependabot/github_actions/dependencies-a3a104477f
chore/simplify-ci-and-makefile
dependabot/go_modules/golang.org/x/crypto-0.45.0
dependabot/go_modules/github.com/go-viper/mapstructure/v2-2.4.0
panekj/ci/improve-jobs
fix-skip-non-yaml-files-in-dir
normalize-pull-rebuild-flags
fix-no-recurse-by-default
2517-poor-error-for-incomplete-action-step
2472-make-use-new-action-cache-the-new-default-for-downloading-actions
act-tart
act-lxc
act-oidc
act-dind
avoid-slash-in-actor
dependabot/go_modules/github.com/docker/docker-26.1.4incompatible
meta-keep-filetime
local-repository-action-cache
pr-merger
update-docker-deps
follow_local_action_symlink
boltdb-lock-in-handler
use-socket-path
no-pull-no-rebuild
path-issues
fix/env
feat/podman
refactor/testdata
v0.2.87
v0.2.86
v0.2.85
v0.2.84
v0.2.83
v0.2.82
v0.2.81
v0.2.80
v0.2.79
v0.2.78
v0.2.77
v0.2.76
v0.2.75
v0.2.74
v0.2.73
v0.2.72
v0.2.71
v0.2.70
v0.2.69
v0.2.68
v0.2.67
v0.2.66
v0.2.65
v0.2.64
v0.2.63
v0.2.62
v0.2.61
v0.2.60
v0.2.59
v0.2.58
v0.2.57
v0.2.56
v0.2.55
v0.2.54
v0.2.53
v0.2.52
v0.2.51
v0.2.50
v0.2.49
v0.2.48
v0.2.47
v0.2.46
v0.2.45
v0.2.44
v0.2.43
v0.2.42
v0.2.41
v0.2.40
v0.2.39
v0.2.38
v0.2.37
v0.2.36
v0.2.35
v0.2.34
v0.2.33
v0.2.32
v0.2.31
v0.2.30
v0.2.29
v0.2.28
v0.2.27
v0.2.26
v0.2.25
v0.2.24
v0.2.23
v0.2.22
v0.2.21
v0.2.20
v0.2.19
v0.2.18
v0.2.17
v0.2.16
v0.2.15
v0.2.14
v0.2.13
v0.2.12
v0.2.11
v0.2.10
v0.2.9
v0.2.8
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.3
v0.1.2
v0.1.1
v0.1.0
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels   
area/action

   
area/cli

   
area/docs

   
area/image

   
area/runner

   
area/workflow

   
backlog

   
confirmed/not-planned

   
kind/bug

   
kind/discussion

   
kind/external

   
kind/feature-request

   
kind/question

   
meta/duplicate

   
meta/invalid

   
meta/need-more-info

   
meta/resolved

   
meta/wontfix

   
meta/workaround

   
needs-work

   
pull-request

Mirrored from GitHub Pull Request

  
review/not-planned

   
size/M

   
size/XL

   
size/XXL

   
stale

   
stale-exempt
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#1036
No description provided.