Repository navigation
ci: give kernel planning and build lookup 30 minutes - #195
Merged
Merged
Conversation
The ten-minute planning budget has expired during earlier-build lookup on the PR182 queue run, PR182's first requested build, and the PR171 queue run. Slow sparse checkouts alone used six to eight minutes of it. Give planning thirty minutes while keeping a hard deadline. No build or test deadlines, permissions, artifact checks or result requirements change. Signed-off-by: Chris Kearney <303316+chriskearney@users.noreply.github.com> Generated-by: LLM
scottjones
approved these changes
Oct 23, 2026
scottjones
left a comment
Collaborator
There was a problem hiding this comment.
Looks good: both cited runs died at the 10-minute plan limit. Longer term, the 6-8 minute sparse checkout looks like the thing to shrink.
[Medium impact] This PR appears safe to merge. SummaryRaises
Reviews (1) · Last reviewed commit: "ci: allow time for kernel planning and b..." · Reviewed by Greptile |
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.
Kernel CI has repeatedly hit the planning job's ten-minute limit before a full build can start. This raises that job's budget to 30 minutes, covering the sparse checkout, packaging-input fetch and baseline/build lookup.
Confirmed instances:
The separate full #182 build has passed, including package, KUnit and boot checks. This addresses its independent merge-queue preparation failure.
Only
jobs.plan.timeout-minuteschanges, plus an explanatory comment. Package/test deadlines, permissions, artifact trust checks and the requiredci / resultbehavior are unchanged; the job still has a hard deadline.Validation:
-shellcheck=(the host ShellCheck cannot load its shared library; no shell code changed).git diff --checkpasses.Merge Danger: two-way. Scope is CI preparation only; a stalled planning job can now occupy a runner for up to 30 minutes instead of ten. No kernel code or release artifacts change.