starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 01:15:51 +03:00

[GH-ISSUE #833] Frozen local run with no indication of error #505

New issue

Closed

opened 2026-03-01 21:44:01 +03:00 by kerem · 2 comments

kerem commented

2026-03-01 21:44:01 +03:00

Owner

Originally created by @lermana on GitHub (Oct 4, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/833

Background

Hello! Really enjoying act so far -- thanks.

I am trying to run a test job (which runs unit tests in Python 3) as part of a workflow. The other part of the workflow (which I'd like to have depend on the tests passing) works fine. The test job, however, seems to just hang, and without any indication of a failure. This test job runs fine in live GitHub Actions.

I searched for open issues containing "frozen" or "stuck" in the title and didn't see any, so thought I'd make a ticket.

System information

Operating System: macOS 11.6
Architecture: x64 (64-bit)
Apple M1: no
Docker version: 20.10.8
Docker image used in act: catthehacker/ubuntu:act-latest
act version: act version 0.2.24

Expected behaviour

These tests should run to completion. In GitHub Actions (or when run locally), I get something like the following in std out:

 -- Docs: https://docs.pytest.org/en/stable/warnings.html
================== 104 passed, 2 warnings in 62.72s (0:01:02) ==================

Additionally, in GitHub Actions, I see "Post job cleanup." pertaining to checkout@v2:

Post job cleanup.
/usr/bin/git version
git version 2.33.0

For reference, the Actions run is generally done, start-to-finish, in around 2.5mins.

Actual behaviour

Unfortunately, the command I'm running just ... hangs, for a really long time (like 10min+, easily).

Here is semi-redacted output log:

[package/test] 🚀  Start image=catthehacker/ubuntu:act-latest
[package/test]   🐳  docker run image=catthehacker/ubuntu:act-latest platform= entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[package/test]   🐳  docker exec cmd=[mkdir -m 0777 -p /var/run/act] user=root
[package/test]   🐳  docker cp src=/Users/user/package/.github/workflows/. dst=/Users/user/package/.github/workflows
[package/test]   🐳  docker exec cmd=[mkdir -p /Users/user/package/.github/workflows] user=
[package/test] ⭐  Run actions/checkout@v2
[package/test]   ✅  Success - actions/checkout@v2
[package/test] ⭐  Run Unit tests
[package/test]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /Users/user/package/.github/workflows/workflow/1] user=

Additionally, I can exec into the hanging container, but when I try to look into what's happening, I find an empty folder:

# laptop

user ~/package/.github/workflows [branch] $ docker ps

CONTAINER ID   IMAGE                            COMMAND                  CREATED          STATUS          PORTS     NAMES
316a25122d23   catthehacker/ubuntu:act-latest   "/usr/bin/tail -f /d…"   39 minutes ago   Up 39 minutes             act-metaplay-interface-test

user ~/package/.github/workflows [branch] $ docker exec -it 316a25122d23 /bin/bash

# container

root@docker-desktop:/Users/user/package/.github/workflows# ps -aux 
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0   2552   576 pts/0    Ss+  16:54   0:00 /usr/bin/tail -f /dev/null
root        21  0.0  0.1   3984  2800 pts/3    Ss+  16:54   0:00 bash --noprofile --norc -e -o pipefail /Users/user/package/.github/workflows/workflow/1
root       344  0.0  0.1   5992  3768 pts/3    S+   16:55   0:00 sudo apt-get install python3.8
root       345  0.0  3.0  68560 61084 pts/3    S+   16:55   0:01 apt-get install python3.8
root       350  0.5  0.1   4248  3440 pts/1    Ss   17:27   0:00 /bin/bash
root       360  0.0  0.1   5904  2828 pts/1    R+   17:27   0:00 ps -aux

root@docker-desktop:/Users/user/package/.github/workflows# ls /Users/user/package
root@docker-desktop:/Users/user/package/.github/workflows#

Workflow and/or repository

name: private-workflow

on: push

jobs:

  test:
    runs-on: ubuntu-latest
    env:
          AWS_REGION: us-east-2
          EKS_CLUSTER_NAME: test
    steps:
      - uses: actions/checkout@v2
      - name: Unit tests
        run: |
          sudo apt-get update > /dev/null
          sudo apt-get install python3.8 > /dev/null
          sudo apt-get install python3-pip > /dev/null
          pip3 install -q virtualenv
          python3 -m virtualenv -p python3.8 -q $GITHUB_WORKSPACE/env
          source $GITHUB_WORKSPACE/env/bin/activate > /dev/null
          pip install -q setuptools pytest
          pip install -q other libs
          pip install -q $GITHUB_WORKSPACE/package/
          export CREATE_ON_START=FALSE
          (cd $GITHUB_WORKSPACE/package && python setup.py test)

Originally created by @lermana on GitHub (Oct 4, 2021). Original GitHub issue: https://github.com/nektos/act/issues/833 ## Background Hello! Really enjoying `act` so far -- thanks. I am trying to run a test job (which runs unit tests in Python 3) as part of a workflow. The other part of the workflow (which I'd like to have depend on the tests passing) works fine. The test job, however, seems to just hang, and without any indication of a failure. This test job runs fine in live GitHub Actions. I searched for open issues containing `"frozen"` or `"stuck"` in the title and didn't see any, so thought I'd make a ticket. ## System information - Operating System: macOS 11.6 - Architecture: x64 (64-bit) - Apple M1: no - Docker version: `20.10.8` - Docker image used in `act`: `catthehacker/ubuntu:act-latest` - `act` version: `act version 0.2.24` ## Expected behaviour These tests should run to completion. In GitHub Actions (or when run locally), I get something like the following in std out: ``` -- Docs: https://docs.pytest.org/en/stable/warnings.html ================== 104 passed, 2 warnings in 62.72s (0:01:02) ================== ``` Additionally, in GitHub Actions, I see `"Post job cleanup."` pertaining to `checkout@v2`: ``` Post job cleanup. /usr/bin/git version git version 2.33.0 ``` For reference, the Actions run is generally done, start-to-finish, in around 2.5mins. ## Actual behaviour Unfortunately, the command I'm running just ... hangs, for a really long time (like 10min+, easily). Here is semi-redacted output log: ``` [package/test] 🚀 Start image=catthehacker/ubuntu:act-latest [package/test] 🐳 docker run image=catthehacker/ubuntu:act-latest platform= entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[] [package/test] 🐳 docker exec cmd=[mkdir -m 0777 -p /var/run/act] user=root [package/test] 🐳 docker cp src=/Users/user/package/.github/workflows/. dst=/Users/user/package/.github/workflows [package/test] 🐳 docker exec cmd=[mkdir -p /Users/user/package/.github/workflows] user= [package/test] ⭐ Run actions/checkout@v2 [package/test] ✅ Success - actions/checkout@v2 [package/test] ⭐ Run Unit tests [package/test] 🐳 docker exec cmd=[bash --noprofile --norc -e -o pipefail /Users/user/package/.github/workflows/workflow/1] user= ``` Additionally, I can `exec` into the hanging container, but when I try to look into what's happening, I find an empty folder: ``` # laptop user ~/package/.github/workflows [branch] $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 316a25122d23 catthehacker/ubuntu:act-latest "/usr/bin/tail -f /d…" 39 minutes ago Up 39 minutes act-metaplay-interface-test user ~/package/.github/workflows [branch] $ docker exec -it 316a25122d23 /bin/bash # container root@docker-desktop:/Users/user/package/.github/workflows# ps -aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 2552 576 pts/0 Ss+ 16:54 0:00 /usr/bin/tail -f /dev/null root 21 0.0 0.1 3984 2800 pts/3 Ss+ 16:54 0:00 bash --noprofile --norc -e -o pipefail /Users/user/package/.github/workflows/workflow/1 root 344 0.0 0.1 5992 3768 pts/3 S+ 16:55 0:00 sudo apt-get install python3.8 root 345 0.0 3.0 68560 61084 pts/3 S+ 16:55 0:01 apt-get install python3.8 root 350 0.5 0.1 4248 3440 pts/1 Ss 17:27 0:00 /bin/bash root 360 0.0 0.1 5904 2828 pts/1 R+ 17:27 0:00 ps -aux root@docker-desktop:/Users/user/package/.github/workflows# ls /Users/user/package root@docker-desktop:/Users/user/package/.github/workflows# ``` ## Workflow and/or repository ``` name: private-workflow on: push jobs: test: runs-on: ubuntu-latest env: AWS_REGION: us-east-2 EKS_CLUSTER_NAME: test steps: - uses: actions/checkout@v2 - name: Unit tests run: | sudo apt-get update > /dev/null sudo apt-get install python3.8 > /dev/null sudo apt-get install python3-pip > /dev/null pip3 install -q virtualenv python3 -m virtualenv -p python3.8 -q $GITHUB_WORKSPACE/env source $GITHUB_WORKSPACE/env/bin/activate > /dev/null pip install -q setuptools pytest pip install -q other libs pip install -q $GITHUB_WORKSPACE/package/ export CREATE_ON_START=FALSE (cd $GITHUB_WORKSPACE/package && python setup.py test) ```

kerem

2026-03-01 21:44:01 +03:00

closed this issue
added the
kind/bug

meta/resolved
labels

kerem commented

2026-03-01 21:44:02 +03:00

Author

Owner

@catthehacker commented on GitHub (Oct 4, 2021):

change apt-get update/install to apt-get update/install -yq

@catthehacker commented on GitHub (Oct 4, 2021): change `apt-get update/install` to `apt-get update/install -yq`

kerem commented

2026-03-01 21:44:02 +03:00

Author

Owner

@lermana commented on GitHub (Oct 4, 2021):

that did it -- thanks!

@lermana commented on GitHub (Oct 4, 2021): that did it -- thanks!

kerem referenced this issue

2026-03-01 21:51:20 +03:00

[PR #505] [CLOSED] Fix readme #1475

No milestone

No project

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#505

No description provided.

Rows
Columns