Document whether timeout-minutes includes runner queue time, and the "not acquired" cancellation

未关闭
  • 哪里不对？
#46,930 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
57/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
github-actions, typescript
领域
documentation

调研方向

Start with the linked timeout-minutes section in the workflow syntax article and check the cited workflow runs and community reports for evidence about queue time and the “not acquired” cancellation. Confirm the behavior with the relevant documentation or source available in the repository before editing. Done means the section clearly explains whether hosted runner queue time counts, describes this cancellation and its remedy, and distinguishes it from the configured timeout.

由索引模型根据 Issue 内容生成。

描述

triage
Code of Conduct
What article on docs.github.com is affected?

https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idtimeout-minutes

What part(s) of the article would you like to see updated?

The section says timeout-minutes is "the maximum number of minutes to let a job run before GitHub automatically cancels it." It doesn't say whether time spent queued for a GitHub-hosted runner counts toward that limit.

It also doesn't mention that GitHub can cancel a hosted job that never gets a runner. I hit both on 2026-11-12 and couldn't tell from the docs which one cancelled my job.

My macos-latest job had timeout-minutes: 15 and was cancelled twice, exactly 15m01s after it was created, with no runner assigned and no steps run:

Both carry the annotations "The job was not acquired by Runner of type hosted even after multiple attempts" and "Due to capacity constraints, jobs targeting macOS arm64 runners may experience longer queue times." The 15-minute match made it look like my timeout fired, so I first planned to move the limit to step level. jm2/kisakcod#838 shows a job with a 90-minute timeout cancelled the same way after about 28 minutes, which suggests the timeout wasn't the cause.

Could the section state:

  1. whether queue time counts toward timeout-minutes on GitHub-hosted runners, and
  2. that a hosted job can be cancelled with the "not acquired" annotation when no runner is available, regardless of timeout-minutes, and that re-running it is the remedy?
Additional information

Other repositories report the same pattern for macOS arm64 jobs, for example https://github.com/orgs/community/discussions/211885 and https://github.com/orgs/community/discussions/212069. If the cancellation follows a fixed acquisition limit, putting that number in the docs would help people tell it apart from their own timeout.

主要语言
TypeScript
星标
21.4k
派生
69.5k
平均合并
14 小时 31 分钟
30 天内合并 PR
90

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

github/docs 的其他 Issue

查看 github/docs 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。