GitHub Community
-
|
I’ve noticed more than expected consumption of my organization’s GitHub Actions monthly minutes for the past few days. Today I found what I believe to be the cause. We don’t explicitly set |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
@chingc ， There are few notes need you pay attention to:
According above two points, the below situations (including but not limited to) will let the workflow run be matked as timed out after 72 hours:
More details about the limits of time-out, you can reference here: https://help.github.com/en/actions/getting-started-with-github-actions/about-github-actions#usage-limits |
Beta Was this translation helpful? Give feedback.
-
|
I just got the error:
On a self-hosted runner. You actually need to set `jobs.JOB_UID.minutes" to change the default 360 minute timeout. More information here: https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes |
Beta Was this translation helpful? Give feedback.
@chingc ，
There are few notes need you pay attention to:
When using GitHub-hosted runner to run jobs in the workflow, each jobs can run for up to 6 hours （360 minutes） of execution time, , but this limit does not apply to self-hosted runners.
Each workflow run is limited to 72 hours. If a workflow run reaches this limit, the workflow run is cancelled. This limit also applies to self-hosted runners.
According above two points, the below situations (including but not limited to) will let the workflow run be matked as timed out after 72 hours:
When using GitHub-hosted runners to run some performed sequentially jobs (at least 12) in the workflow, and the total run time of the jobs rea…