Skip to content

Raise pr-review job timeout to 30 minutes - #108

Merged
gontzess merged 2 commits into
mainfrom
gontzess/pr-review-timeout-30
Aug 7, 2026
Merged

Raise pr-review job timeout to 30 minutes#108
gontzess merged 2 commits into
mainfrom
gontzess/pr-review-timeout-30

Conversation

@gontzess

@gontzess gontzess commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Why

The reviewer model is now claude-opus-5, which runs longer per review than opus-4-8 (and the automatic cybersecurity→opus-4.8 safety fallback can stack a second run into the same job). On the ductone side the same model bump drove judge PR-review timeouts from 0/809 runs to 20/191 (10.5%) against a 15-minute cap — cancelled mid-review, surfacing as a "did not finish in time … not a verdict" notice rather than a real verdict. This raises the caps here before the same regression shows up.

What this changes

Raises timeout-minutes to 30 on both PR-review reusable-workflow jobs: pr-review.yaml (15→30) and general-pr-review.yaml (20→30). Trade-off: a longer-running or wedged review now uses up to 30 runner-minutes before being cut off.

The opus-5 reviewer runs longer per review than opus-4-8, and the pr-review (15m) and general-pr-review (20m) caps were cancelling reviews mid-run (they surface as a 'did not finish in time' non-verdict). Raise both to 30 minutes.
Moves the pin from v1.0.130 (109 commits behind) to v1.0.185. Net-hardening: stronger untrusted-content sanitization and token redaction, plus the #1350 fix for the silent Bash-permission-widening parser bug that v1.0.130 lacked. No new default token perms or tool exposure for our config. Replaces the bare SHA with a SHA + version comment (still pinned, not @v1).
@gontzess
gontzess merged commit 2eccaff into main Aug 7, 2026
2 checks passed
@gontzess
gontzess deleted the gontzess/pr-review-timeout-30 branch August 7, 2026 19:14
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.

3 participants