fix: align benchmark agent settings and enforce MiniSWE output budget - #70
fix: align benchmark agent settings and enforce MiniSWE output budget#70Yofuria wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe MiniSWE wrapper now forwards ChangesMiniSWE output limit
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: 🔵 Low · up to The change enforces a runtime output-token override for MiniSWE models, but the setting has no explicit maximum, so a misconfigured value could increase execution time or cost beyond the intended budget. The PR is mergeable with owner awareness or follow-up to document the trusted configuration owner and bound the allowed value. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Aligns benchmark recipes with the audited target/mutation agent settings and makes
MINISWE_MAX_OUTPUT_LIMITan enforced runtime override in the candidate adapter.Validation:
max_output_tokens=10000,cost_limit=3.0, andreasoning.effort=highSummary by CodeRabbit
New Features
MINISWE_MAX_OUTPUT_LIMITenvironment setting.Bug Fixes