Repository navigation
ci(release): raise release validation timeout to 150 minutes - #3396
Conversation
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>
|
/review |
|
✅ AI Code Review Complete requested by @integry Posted 1 review: |
🔍 AI Code Review — codex:gpt-6-astraOverall EvaluationThe PR correctly raises only ✅ Precisely scoped change — ✅ 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 blockersNo merge blockers. SuggestionsThese are optional follow-ups and are not sent to S1: 🟢 Measure completed validation durationRecord 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. ScoreThe 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
Copy and edit to choose records from this review: 🤖 Review by ProPR |
The
v0.9.0tag run (41112918338) was cancelled at exactly 60 minutes inside Run full server and UI suites:validate-releasehastimeout-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-releasetimeout to 150 minutes. Other jobs already have enough headroom (build/smoke/push 180, the rest 15–60). After merge the release is re-run withworkflow_dispatch(expected_version=0.9.0), which checks out and verifies the existingv0.9.0tag.🤖 Generated with Claude Code