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

Ouverte
  • Quelque chose ne va pas ?
#46,930 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
57/100
Type d'issue
Documentation
Clarté
Plutôt claire
Activité
Active
Stack technique
github-actions, typescript
Domaine
documentation

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
21.4k
Forks
69.5k
Merge moyen
14 h 31 min
PR mergées (30 j)
90

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de github/docs

Toutes les issues de github/docs

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.