Skip to content

fix(eval): raise triage max_turns budget from 30 to 35 #967

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
waynesun09 wants to merge 1 commit into from
Closed

fix(eval): raise triage max_turns budget from 30 to 35 #967

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion eval/triage/cases/001-bug-url-encoding/annotations.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ labels:
- ready-to-code
- bug

max_turns: 30
max_turns: 35

@qodo-code-review qodo-code-review Bot Aug 23, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Informational

1. Weaker turn-regression gate 🐞 Bug ⚙ Maintainability

Raising max_turns to 35 makes the triage eval stop failing runs that take 31–35 turns, so a
turn-count regression in that band will no longer be caught by the max_turns judge. Only other
constraints (e.g., max_cost_usd or harness timeouts) will catch those regressions.

max_cost_usd: 2.00

# Guidance for the LLM judge — what a good triage looks like for this case.
Expand Down
2 changes: 1 addition & 1 deletion eval/triage/cases/002-needs-info-vague-crash/annotations.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ labels:
- ready-to-code
- triaged

max_turns: 30
max_turns: 35
max_cost_usd: 2.00

triage_expectations: |
Expand Down
2 changes: 1 addition & 1 deletion eval/triage/cases/003-feature-request/annotations.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ labels:
- ready-to-code
- needs-info

max_turns: 30
max_turns: 35
max_cost_usd: 2.00

triage_expectations: |
Expand Down
2 changes: 1 addition & 1 deletion eval/triage/cases/004-duplicate-issue/annotations.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ labels:
- needs-info
- triaged

max_turns: 30
max_turns: 35
max_cost_usd: 2.00

triage_expectations: |
Expand Down
2 changes: 1 addition & 1 deletion eval/triage/cases/005-not-planned-out-of-scope/annotations.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ labels:
- triaged
- feature

max_turns: 30
max_turns: 35
max_cost_usd: 2.00

triage_expectations: |
Expand Down
2 changes: 1 addition & 1 deletion eval/triage/cases/006-not-planned-guardrail/annotations.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ labels:
- ready-to-code
- needs-info

max_turns: 30
max_turns: 35
max_cost_usd: 2.00

triage_expectations: |
Expand Down
2 changes: 1 addition & 1 deletion eval/triage/cases/007-self-evident-bug-redundancy/annotations.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ labels:
- ready-to-code
- bug

max_turns: 30
max_turns: 35
max_cost_usd: 2.00

triage_expectations: |
Expand Down
2 changes: 1 addition & 1 deletion eval/triage/cases/008-split-bundled-issues/annotations.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ labels:
- triaged
- blocked

max_turns: 30
max_turns: 35
max_cost_usd: 2.00

triage_expectations: |
Expand Down
Loading