Skip to content

ci: give kernel planning and build lookup 30 minutes - #195

Merged
scottjones merged 1 commit into
integration/aurorafrom
fix/ci-plan-timeout-20261023
Oct 23, 2026
Merged

scottjones merged 1 commit into
integration/aurorafrom
fix/ci-plan-timeout-20261023

Conversation

@chriskearney

Copy link
Copy Markdown

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-minutes changes, plus an explanatory comment. Package/test deadlines, permissions, artifact trust checks and the required ci / result behavior are unchanged; the job still has a hard deadline.

Validation:

  • CI unit tests: 112 passed.
  • actionlint 1.7.12 workflow validation passed with -shellcheck= (the host ShellCheck cannot load its shared library; no shell code changed).
  • Parsed-YAML comparison confirms that the planning timeout is the only semantic change; git diff --check passes.

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.

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 scottjones left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@greptile-apps

greptile-apps Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] This PR appears safe to merge.

Summary

Raises jobs.plan.timeout-minutes from 10 to 30 minutes and adds a comment explaining why.

  • Kernel CI planning can now run for up to 30 minutes.

Reviews (1) · Last reviewed commit: "ci: allow time for kernel planning and b..." · Reviewed by Greptile

@scottjones
scottjones added this pull request to the merge queue Oct 23, 2026
Merged via the queue into integration/aurora with commit b6d81ea Oct 23, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants