[GH-ISSUE #1398] act has no output #736

Closed
opened 2026-03-01 21:45:57 +03:00 by kerem · 3 comments
Owner

Originally created by @lorensr on GitHub (Oct 18, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1398

Bug report info

$ act bug-report
WARN  ⚠ You are using Apple M1 chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. ⚠ 

$ act --version
act version 0.2.32

$ which act
/opt/homebrew/bin/act

Command used with act

act lint-and-prune --container-architecture linux/amd64

Describe issue

Output from the steps' stdout and output describing what steps were taken.

github.com/temporalio/sdk-typescript@91f3c23761/.github/workflows/ci.yml

Workflow content

name: Continuous Integration

on:
  pull_request:

jobs:
  lint-and-prune:
    runs-on: ubuntu-latest
    steps:
      - run: echo 'start'
      - run: echo 'done'

Relevant log output

$ act lint-and-prune -v --container-architecture linux/amd64
DEBU[0000] Loading environment from /Users/me/gh/sdk3/.env 
DEBU[0000] Loading secrets from /Users/me/gh/sdk3/.secrets 
DEBU[0000] Loading workflows from '/Users/me/gh/sdk3/.github/workflows' 
DEBU[0000] Loading workflows recursively                
DEBU[0000] Found workflow 'ci.yml' in '/Users/me/gh/sdk3/.github/workflows/ci.yml' 
DEBU[0000] Reading workflow '/Users/me/gh/sdk3/.github/workflows/ci.yml' 
DEBU[0000] Using first passed in arguments event for filtering: lint-and-prune 
DEBU[0000] Preparing plan for a event: lint-and-prune   
DEBU[0000] Using first passed in arguments event: lint-and-prune 
DEBU[0000] Planning jobs for event: lint-and-prune

Additional information

No response

Originally created by @lorensr on GitHub (Oct 18, 2022). Original GitHub issue: https://github.com/nektos/act/issues/1398 ### Bug report info ```plain text $ act bug-report WARN ⚠ You are using Apple M1 chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. ⚠ $ act --version act version 0.2.32 $ which act /opt/homebrew/bin/act ``` ### Command used with act ```sh act lint-and-prune --container-architecture linux/amd64 ``` ### Describe issue Output from the steps' stdout and output describing what steps were taken. ### Link to GitHub repository https://github.com/temporalio/sdk-typescript/blob/91f3c237618121c55d28967053dfc14fc5947f70/.github/workflows/ci.yml ### Workflow content ```yml name: Continuous Integration on: pull_request: jobs: lint-and-prune: runs-on: ubuntu-latest steps: - run: echo 'start' - run: echo 'done' ``` ### Relevant log output ```sh $ act lint-and-prune -v --container-architecture linux/amd64 DEBU[0000] Loading environment from /Users/me/gh/sdk3/.env DEBU[0000] Loading secrets from /Users/me/gh/sdk3/.secrets DEBU[0000] Loading workflows from '/Users/me/gh/sdk3/.github/workflows' DEBU[0000] Loading workflows recursively DEBU[0000] Found workflow 'ci.yml' in '/Users/me/gh/sdk3/.github/workflows/ci.yml' DEBU[0000] Reading workflow '/Users/me/gh/sdk3/.github/workflows/ci.yml' DEBU[0000] Using first passed in arguments event for filtering: lint-and-prune DEBU[0000] Preparing plan for a event: lint-and-prune DEBU[0000] Using first passed in arguments event: lint-and-prune DEBU[0000] Planning jobs for event: lint-and-prune ``` ### Additional information _No response_
kerem 2026-03-01 21:45:57 +03:00
Author
Owner

@KnisterPeter commented on GitHub (Oct 18, 2022):

Please read this
https://github.com/nektos/act#example-commands

<!-- gh-comment-id:1281821359 --> @KnisterPeter commented on GitHub (Oct 18, 2022): Please read this https://github.com/nektos/act#example-commands
Author
Owner

@lorensr commented on GitHub (Oct 18, 2022):

Ah, I see. What do you think about outputting what event is being
triggered, and whether that matches an on: in the workflow?

On Tue, Oct 18, 2022 at 1:08 AM Markus Wolf @.***>
wrote:

Closed #1398 https://github.com/nektos/act/issues/1398 as not planned.


Reply to this email directly, view it on GitHub
https://github.com/nektos/act/issues/1398#event-7607798040, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB5LGDZXNXTALGX3F6YJCTWDYWDJANCNFSM6AAAAAARHVW5PQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1281827977 --> @lorensr commented on GitHub (Oct 18, 2022): Ah, I see. What do you think about outputting what event is being triggered, and whether that matches an `on:` in the workflow? On Tue, Oct 18, 2022 at 1:08 AM Markus Wolf ***@***.***> wrote: > Closed #1398 <https://github.com/nektos/act/issues/1398> as not planned. > > — > Reply to this email directly, view it on GitHub > <https://github.com/nektos/act/issues/1398#event-7607798040>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAB5LGDZXNXTALGX3F6YJCTWDYWDJANCNFSM6AAAAAARHVW5PQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@KnisterPeter commented on GitHub (Oct 18, 2022):

Feel free the open a pull request with that change.

<!-- gh-comment-id:1281828580 --> @KnisterPeter commented on GitHub (Oct 18, 2022): Feel free the open a pull request with that change.
Sign in to join this conversation.
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#736
No description provided.