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

Aperta
  • Qualcosa non va?
#46,930 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
57/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, typescript
Ambito
documentation

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
21.4k
Fork
69.5k
Merge medio
14h 31m
PR unite (30g)
90

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/docs

Tutte le issue di github/docs

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.