fix(schema-consistency-checker): replace max-turns with max-effective-tokens 20M and reduce turn waste#31258
Conversation
…efficiency guidance The workflow was hitting the 60-turn limit on 5/7 days; the one successful run (May 6) used 101 turns. Changes: - Raise max-turns: 60 → 120 in frontmatter - Add "Turn Budget" section encouraging batched bash calls - Merge schema-diff + strategy-cache read into one Step 0 command - Fix indentation in the combined bash example - Clarify that for-loop field names are placeholders from field_gaps - Renumber steps (6 → 5 after merging Step 0/1) - Recompile lock file Agent-Logs-Url: https://github.com/github/gh-aw/sessions/1c3adc73-1057-42a0-a18a-053cc476418d Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
|
@copilot remove max-turns and replace with max-effective-tokens 20M |
…-tokens 20M Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Done — |
There was a problem hiding this comment.
Pull request overview
Updates the schema-consistency-checker workflow configuration to reduce failures caused by hitting execution limits, primarily by shifting from a turn-based cap to an effective-token budget and by reducing wasted turns in the prompt instructions.
Changes:
- Swaps the workflow budgeting approach from
engine.max-turnsto an effective-token budget and adds guidance to conserve turns/tool calls. - Merges the “read pre-computed data” and “load strategies” steps into a single batched bash command in the instructions.
- Recompiles the workflow lock file to remove
--max-turns/GH_AW_MAX_TURNSand update the effective-token budget env var.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/schema-consistency-checker.md | Updates workflow frontmatter and prompt instructions to change budgeting strategy and reduce tool-call waste. |
| .github/workflows/schema-consistency-checker.lock.yml | Recompiled lock to remove max-turns wiring and update effective-token budget configuration. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 3
| harness: | ||
| budget: | ||
| max-effective-tokens: 20000000 |
| ## Turn Budget | ||
|
|
||
| You have a maximum turn budget. **Spend turns wisely**: |
| GH_AW_MISSING_DATA_REPORT_AS_FAILURE: "true" | ||
| GH_AW_TIMEOUT_MINUTES: "30" | ||
| GH_AW_MAX_EFFECTIVE_TOKENS: "10000000" | ||
| GH_AW_MAX_EFFECTIVE_TOKENS: "20000000" | ||
| GH_AW_CACHE_MEMORY_ENABLED: "true" |
The schema-consistency-checker has been failing
error_max_turnson 5/7 days. The one successful run (May 6) consumed 101 turns — 68% over the 60-turn cap.Changes
max-turnswithharness.budget.max-effective-tokens: 20000000— switches from a turn-count budget to a 20 M token budget, giving the workflow reliable headroom without an arbitrary turn ceilingfield_gaps(pre-computed, zero discovery cost), and skip low-signal categories rather than exhaustively covering all four areas every run--max-turnsCLI flag andGH_AW_MAX_TURNSenv var; updatesGH_AW_MAX_EFFECTIVE_TOKENSto"20000000"