Skip to content

feat(swe-bench): eval-phase infra-vs-genuine error classifier - #472

Open
arekay-nv wants to merge 1 commit into
swe-layer-3from
swe-layer-4
Open

feat(swe-bench): eval-phase infra-vs-genuine error classifier#472
arekay-nv wants to merge 1 commit into
swe-layer-3from
swe-layer-4

Conversation

@arekay-nv

Copy link
Copy Markdown
Collaborator

What does this PR do?

Type of change

  • Bug fix
  • New feature
  • Documentation update
  • Refactor/cleanup

Related issues

Testing

  • Tests added/updated
  • All tests pass locally
  • Manual testing completed

Checklist

  • Code follows project style
  • Pre-commit hooks pass
  • Documentation updated (if needed)

Stack created with GitHub Stacks CLIGive Feedback 💬

The Pyxis sentinel only covers the agent phase; eval-phase error_ids were
counted as real outcomes and never retried, which is what produced 24 of 25
permanently-bad runs on the source cluster. classify.py reads the SWE-bench
report's error_ids and each instance's run_instance.log and classifies them
through an ORDERED rule list, first match wins. The order is load-bearing:
BuildImageError is checked before everything because its message embeds the
other rules' needles, CONMON_EAGAIN and TEST_TIMEOUT precede WEDGE_EVAL, and
PATCH_APPLY_FAILED is last.

Anything unclassifiable is UNKNOWN and UNKNOWN is GENUINE, asserted by a
membership test: a false bad-run costs one redo, a false retry biases the
measurement toward optimism.

Memory-kill markers are consumed by phase - an eval-phase kill is a genuine
failure (an unbounded allocation is a failing patch), an agent-phase kill is
recorded for audit only, since the agent merely gets an error observation
and the instance still reaches a real outcome.
@arekay-nv
arekay-nv requested a review from a team as a code owner August 26, 2026 03:32
@github-actions

Copy link
Copy Markdown

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

@github-actions
github-actions Bot requested a review from nvzhihanj August 26, 2026 03:32
@github-actions github-actions Bot added the size/normal PR Review Policy: <=500 non-test lines & <=20 files label Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/normal PR Review Policy: <=500 non-test lines & <=20 files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants