Skip to content

ci(release): raise release validation timeout to 150 minutes - #3396

Merged
integry merged 1 commit into
mainfrom
release/validate-timeout
Oct 30, 2026
Merged

integry merged 1 commit into
mainfrom
release/validate-timeout

Conversation

@integry

@integry integry commented Oct 30, 2026

Copy link
Copy Markdown
Owner

The v0.9.0 tag run (41112918338) was cancelled at exactly 60 minutes inside Run full server and UI suites: validate-release has timeout-minutes: 60, and the unsharded full suite (945 units) now takes over an hour on a hosted runner. v0.8.15's validation took 10 minutes. Nothing was published (all publish jobs were skipped).

This raises only the validate-release timeout to 150 minutes. Other jobs already have enough headroom (build/smoke/push 180, the rest 15–60). After merge the release is re-run with workflow_dispatch (expected_version=0.9.0), which checks out and verifies the existing v0.9.0 tag.

🤖 Generated with Claude Code

The v0.9.0 tag run was cancelled at the 60-minute job timeout while running
the full server and UI suites (945 units), which now take over an hour on a
hosted runner (v0.8.15's validation took 10 minutes). Raise the
validate-release timeout to 150 minutes.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@integry

integry commented Oct 30, 2026

Copy link
Copy Markdown
Owner Author

/review

@propr-dev

propr-dev Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

✅ AI Code Review Complete requested by @integry

Posted 1 review:

View Task Details

@propr-dev

propr-dev Bot commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

🔍 AI Code Review — codex:gpt-6-astra

Overall Evaluation

The PR correctly raises only validate-release’s timeout from 60 to 150 minutes, addressing the reported mid-suite cancellation. It is merge-ready within scope, conditional on completion of the 12 pending checks.

✅ Precisely scoped change — .github/workflows/docker-images.yml:38 increases the validation job’s time budget without changing suite selection, release verification, or downstream publication dependencies.

✅ Preserved validation gates — The full suite must still succeed before dependent release jobs can proceed; extending the timeout does not bypass failures.

Review was based on the supplied diff and context. No commands or tests were run.

Merge blockers

No merge blockers.

Suggestions

These are optional follow-ups and are not sent to /fix.

S1: 🟢 Measure completed validation duration

Record the validation duration from the next successful release run to confirm the 150-minute budget provides adequate headroom. The supplied evidence establishes that 60 minutes was insufficient, but does not establish the full runtime. This is operational follow-up, not a required code change.

Score

The change directly satisfies the stated objective with no identified regression. All 12 current-head checks remain pending; successful release completion under the increased budget is not yet demonstrated.

Score: 9/10


🤖 Review Details

  • Model: GPT-6 Astra
  • Time: 16s
  • Tokens: 24,973 (24,654 in / 319 out)
  • Cost: $0.15

View Task


💡 Next step: Comment /fix to address every F# merge blocker, /fix all for every pending blocker and suggestion, or name records explicitly, as in /fix F3 S5.
F# and S# IDs increment across review comments and remain permanent, so selectors such as /fix F3 F5 stay unambiguous across cycles. S# suggestions stay optional: they are implemented only when you name them or request /fix all, and they never relax a merge blocker.

Copy and edit to choose records from this review:

/fix S1

🤖 Review by ProPR

@integry
integry merged commit c549264 into main Oct 30, 2026
44 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