[CI] Review job: raise turn budget to 60, surface full output on failure - #91
Merged
Merged
Conversation
PR #69 (a diff centered on the 3,000-line ChatTab.tsx) exhausted the 40-turn review budget twice in ~3 minutes without ever reaching the structured-output call, and with show_full_output off the log recorded nothing between init and error_max_turns — undiagnosable by design. Raise the budget to 60 (job timeout still bounds the worst case) and turn on full output so the next exhaustion shows where the turns went. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Auto-merge skippedThis PR touches a path this pipeline always treats as needing a human: Review and merge manually. |
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
1 participant
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.
The auto-review on #69 (diff centered on the 3,000-line ChatTab.tsx) hit
error_max_turnsat 40 twice in ~3 minutes, never reaching the structured-output call — and withshow_full_output: falsethe log shows nothing between init and the error, so the spin can't be diagnosed.--max-turns 40→60(the 15-minute job timeout still bounds the worst case)show_full_output: trueso the next budget exhaustion shows which turns were spent whereOnce this lands on master, re-running #69's review picks it up via the merge ref.
🤖 Generated with Claude Code