Skip to content

swe-infinite: score unsubmitted miniswe runs as zero#73

Open
catoneone wants to merge 1 commit into
mainfrom
swe-infinite-submission-gating
Open

swe-infinite: score unsubmitted miniswe runs as zero#73
catoneone wants to merge 1 commit into
mainfrom
swe-infinite-submission-gating

Conversation

@catoneone

Copy link
Copy Markdown
Collaborator

Summary

  • Take the patch only from a Submitted run in MiniSWEAgent.solve. Any other terminating status (e.g. LimitsExceeded at the step limit) yields an empty patch — deliberately no container git-diff fallback — matching upstream mini-swe-agent + SWE-bench semantics: no submission = empty patch = score 0.
  • Record step-limit runs as failure_reason: limit_reached_no_submission in env.py for observability (distinct from no_patch_generated).
  • Add exit_status to MiniSWEResult.

Production data (2026-06-30 ~ 07-14, 227 miniswe rollouts): 22.5% hit the step limit without submitting; the diff-harvest fallback in the deployed image let 13 unsubmitted runs score 1.0.

Codex/affent are unchanged: they have no submission protocol, so post-run diff extraction remains their normal patch path.

Test

  • New test_submission_gating.py: 3/3 pass (submitted patch accepted; step-limit and non-submit terminating messages yield empty patch).
  • Existing test_structured_outcomes.py: 21 passed.

Take the patch only from a Submitted run; LimitsExceeded and other
terminating statuses now yield an empty patch with no container git-diff
fallback, matching upstream mini-swe-agent + SWE-bench semantics.
Step-limit runs are recorded as failure_reason limit_reached_no_submission.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant