Workflow was terminated after 360 minutes, but config have set timeout-minutes to 600

The log show task have run 600 minutes, but actually it only run 360 minute

The job running on runner GitHub Actions 2 has exceeded the maximum execution time of 600 minutes.

5h 53m 11s

Isn’t it the second job?

image

Anyway, 6 * 60 minutes = 360 minutes. That is the actual limit for a job as per the documentation:

  • Job execution time - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete.

https://docs.github.com/en/actions/reference/usage-limits-billing-and-administration#usage-limits

The error message

The job running on runner GitHub Actions 2 has exceeded the maximum execution time of 600 minutes.

might simply be outdated, not reflecting the actual limit.

https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes The limit can be changed by config, I have change it to 600, that is why the log show the limit is 600
2021年7月6日 +0800 06:35 Simran via GitHub Support Community githubcommunity@discoursemail.com,写道:

It doesn’t say anything about the hard maximum in the documentation you linked to. Is there any source for it being 600 minutes? Does it only apply to self-hosted runners perhaps?

Yes, you can change the limit. For GitHub hosted runners, the default value corresponds to the maximum value. You can thus only lower the limit, which you’d do to prevent a runaway job from burning through your free or paid minutes.

For self-hosted runners (which you aren’t using), you can set it to a higher (or lower) value. But you aren’t using them, so this is irrelevant to you.

Filed:

I believe that the confusion you’re experiencing is a likely outcome of the current documentation.

Is 600 minutes the hard limit for self-hosted runners? I wonder if higher values might get ignored and the default used instead. There’s another topic where someone says that 360 would be the maximum for self-hosted runners, which may or may not be a bug: