-
Notifications
You must be signed in to change notification settings - Fork 2
fix: Lower resolved_threshold default from 0.8 to 0.0 for dead code benchmarks #6
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.
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1148,30 +1148,9 @@ def run( | |
| console.print("[dim]Use --reset-state or --no-incremental to re-run[/dim]") | ||
| exit_code = 3 | ||
|
|
||
| # Check if anything was resolved (exit code 2) | ||
| # Only check this if we actually evaluated tasks | ||
| if exit_code == 0: | ||
| mcp_resolved = results.summary["mcp"]["resolved"] | ||
| baseline_resolved = results.summary["baseline"]["resolved"] | ||
| mcp_total = results.summary["mcp"]["total"] | ||
| baseline_total = results.summary["baseline"]["total"] | ||
|
|
||
| # Only report "no resolutions" if tasks were actually run | ||
| # If total is 0, no tasks were run (not a failure) | ||
| if (mcp_only and mcp_total > 0 and mcp_resolved == 0) or ( | ||
| baseline_only and baseline_total > 0 and baseline_resolved == 0 | ||
| ): | ||
| console.print("\n[yellow]⚠ No tasks resolved (0% success)[/yellow]") | ||
| exit_code = 2 | ||
| elif not mcp_only and not baseline_only: | ||
| # For full run, check if either had tasks and none were resolved | ||
| if ( | ||
| (mcp_total > 0 or baseline_total > 0) | ||
| and mcp_resolved == 0 | ||
| and baseline_resolved == 0 | ||
| ): | ||
| console.print("\n[yellow]⚠ No tasks resolved by either agent (0% success)[/yellow]") | ||
| exit_code = 2 | ||
| # Resolution check removed — dead code benchmarks use continuous P/R/F1 | ||
| # metrics, not binary resolved gates. Other benchmarks can still use | ||
| # resolved_threshold in their config if needed. | ||
|
Comment on lines
+1151
to
+1153
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Exit code 2 is documented but never set anymore. Hey! So the comment here is great at explaining why the resolution check was removed — makes total sense for dead code benchmarks where hitting 80% precision/recall is unrealistic. But here's the thing: the docstring up at lines 582-588 still tells users that exit code 2 means "No resolutions (evaluation ran but 0% success)". Since that code path is gone now, users reading the help output ( You've got a couple options:
📝 Suggested docstring fix (if removing exit code 2) \b
Exit Codes:
- 0 Success (at least one task resolved)
+ 0 Success
1 Fatal error (invalid config, Docker unavailable, crash)
- 2 No resolutions (evaluation ran but 0% success)
3 Nothing evaluated (all tasks cached/skipped)
130 Interrupted by user (Ctrl+C)🤖 Prompt for AI Agents |
||
|
|
||
| # Exit with determined exit code | ||
| if exit_code != 0: | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.