starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 09:25:54 +03:00

[GH-ISSUE #2659] How to Retrieve Execution Time for Each Job in Act #1201

New issue

Closed

opened 2026-03-01 21:49:39 +03:00 by kerem · 3 comments

kerem commented

2026-03-01 21:49:39 +03:00

Owner

Originally created by @Betty1202 on GitHub (Feb 11, 2025).
Original GitHub issue: https://github.com/nektos/act/issues/2659

Act version

v0.2.74

Feature description

Hello,

I am using Act to run GitHub Actions locally, and I am wondering if there is a way to obtain the execution time for each job, similar to what is displayed on the GitHub Actions web interface. For example, the web interface provides a detailed breakdown of the execution time for each step within a job, as shown in the attached screenshot.

Is there a feature or workaround in Act that allows us to capture or display this information? Any guidance on how to achieve this would be greatly appreciated.

Thank you!

Originally created by @Betty1202 on GitHub (Feb 11, 2025). Original GitHub issue: https://github.com/nektos/act/issues/2659 ### Act version v0.2.74 ### Feature description Hello, I am using Act to run GitHub Actions locally, and I am wondering if there is a way to obtain the execution time for each job, similar to what is displayed on the GitHub Actions web interface. For example, the web interface provides a detailed breakdown of the execution time for each step within a job, as shown in the attached screenshot. ![Image](https://github.com/user-attachments/assets/ed7cbb2c-02b7-472b-a030-23dcb9160c00) Is there a feature or workaround in Act that allows us to capture or display this information? Any guidance on how to achieve this would be greatly appreciated. Thank you!

kerem

2026-03-01 21:49:39 +03:00

closed this issue
added the
kind/feature-request
label

kerem commented

2026-03-01 21:49:39 +03:00

Author

Owner

@ChristopherHX commented on GitHub (Feb 11, 2025):

See https://github.com/nektos/act/issues/2660#issuecomment-2652003109

json logs contains timestamp + start + stop of jobs and steps

@ChristopherHX commented on GitHub (Feb 11, 2025): See https://github.com/nektos/act/issues/2660#issuecomment-2652003109 json logs contains timestamp + start + stop of jobs and steps

kerem commented

2026-03-01 21:49:39 +03:00

Author

Owner

@Betty1202 commented on GitHub (Feb 12, 2025):

Got it. Thanks!

@Betty1202 commented on GitHub (Feb 12, 2025): Got it. Thanks!

kerem commented

2026-03-01 21:49:40 +03:00

Author

Owner

@nobuto-m commented on GitHub (Feb 17, 2025):

I had a similar question and I ended up with a quick hack to print the output of time at the end of each step.

defaults:
  run:
    shell: bash -e -c "/usr/bin/time -f \"\nStep total time:\t%E\" bash -ex {0}"

bash -e -c can be omitted for simplicity. However, actionlint doesn't enable shellcheck if the shell starts with the time command so double bash is a hack to take a balance of both.

@nobuto-m commented on GitHub (Feb 17, 2025): I had a similar question and I ended up with a quick hack to print the output of `time` at the end of each step. ```yaml defaults: run: shell: bash -e -c "/usr/bin/time -f \"\nStep total time:\t%E\" bash -ex {0}" ``` `bash -e -c` can be omitted for simplicity. However, [actionlint](https://github.com/rhysd/actionlint) doesn't enable shellcheck if the shell starts with the time command so double bash is a hack to take a balance of both.

kerem referenced this issue

2026-03-01 21:52:53 +03:00

[PR #1201] [MERGED] build(deps): bump github.com/go-ini/ini from 1.66.5 to 1.66.6 #1833

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

No description provided.

Rows
Columns