Repository navigation
ci: give the two full-history checkout jobs a 15-minute budget - #13126
Merged
iamwhatever merged 1 commit intoSep 23, 2026
Merged
Conversation
PR Scope and CI's 'Detect changed surface' both declare timeout-minutes: 5
and both check out with fetch-depth: 0 because they diff against the merge
base (BASE...HEAD, dorny/paths-filter with local git, the leaf resolver). On
a slow hosted runner the full-history fetch of this repository alone has run
past 5 minutes, and the job is CANCELLED mid-checkout ('The operation was
canceled'): nothing to read, no retry, and on a fork PR another maintainer
release to re-run. Detect changed surface gates every test lane, so its
cancel skipped the whole matrix and failed Coverage Gate (kirodotdev#13111, twice on
kirodotdev#11827 today). 15 minutes covers a slow fetch and still ends a hung one.
The alternative -- a shallow checkout -- would need a separate merge-base
fetch in both jobs and is a larger change than the incident calls for.
Closes kirodotdev#13111
iamwhatever
approved these changes
Sep 23, 2026
wknight1
pushed a commit
to wknight1/KiroCrew
that referenced
this pull request
Oct 5, 2026
…otdev#13126) PR Scope and CI's 'Detect changed surface' both declare timeout-minutes: 5 and both check out with fetch-depth: 0 because they diff against the merge base (BASE...HEAD, dorny/paths-filter with local git, the leaf resolver). On a slow hosted runner the full-history fetch of this repository alone has run past 5 minutes, and the job is CANCELLED mid-checkout ('The operation was canceled'): nothing to read, no retry, and on a fork PR another maintainer release to re-run. Detect changed surface gates every test lane, so its cancel skipped the whole matrix and failed Coverage Gate (kirodotdev#13111, twice on kirodotdev#11827 today). 15 minutes covers a slow fetch and still ends a hung one. The alternative -- a shallow checkout -- would need a separate merge-base fetch in both jobs and is a larger change than the incident calls for. Closes kirodotdev#13111
5 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem / Motivation
PR Scopeand CI'sDetect changed surfaceboth declaretimeout-minutes: 5and both check out withfetch-depth: 0. On a slow hosted runner the full-history fetch of this repository alone has run past 5 minutes and the job is CANCELLED mid-checkout (The operation was canceled) -- twice on #11827 today, both on the first run after a maintainer released the fork hold (#13111).Why it matters
Detect changed surfacegates every test lane, so its cancel skipped the entire matrix and failed Coverage Gate with nothing to read;PR Scopeis a required gate. Neither failure is retried, neither leaves a diagnostic beyond the cancel, and on a fork PR each costs a maintainer another workflow release to re-run.What changed
Symptom: job cancelled during
actions/checkoutat exactly the 5-minute mark, last command the fullgit fetch→ root cause: a 5-minute job budget sized for the job's own work (seconds), not for a full-history fetch of a large repository on a slow runner → change:timeout-minutes: 15on both jobs, each with a comment recording why. The alternative -- a shallow checkout -- would need a separate merge-base fetch in both jobs (BASE...HEADdiffs, dorny/paths-filter with local git, the leaf resolver) and is a larger change than the incident calls for; the budget covers a slow fetch and still ends a hung one.This PR changes workflow files from a fork, so the Fork Workflow-Change Guard will flag it for a maintainer's eyes; the diff is two
timeout-minuteslines plus comments.Backwards compatibility
Compatible: no step, permission or output changes; only the per-job budget grows.
Tests
The eight test files that read
ci.yml/pr-scope.ymlcontracts pass locally (386 tests). No test asserts the 5-minute value.Manual verification
Observe the two jobs on this PR's own run; both should complete well inside the new budget, and the run must not be cancelled at checkout.
Screenshots / video
N/A — no UI change.
Closes #13111