Repository navigation
fix: two false eval stops (quota, Cursor MCP) - #119
AntTheLimey wants to merge 2 commits into
Conversation
A Codex answer saying a repository may have its own quota was filed as infra, which stopped the whole release batch after 34 of 180 runs.
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Grok lists Cursor's built-in server in one arm at random (with in 2 of 3 control runs on 2026-11-05, without in the third), which failed the cross-arm check and blocked the release batch.
What changed
infra_errormatchedquotaanywhere in the stderr-plus-answer textof a run with no tool calls. A Codex Luna answer to task 6 ("...unless
that service or repository has its own quota") was filed as infra, and
the runner stopped the release batch after 34 of 180 runs. A bare
quotanow counts only in stderr; the other limit phrases still matcheither.
cross_arm_problemsnow ignoresMCP:cursor. Cursor's built-inserver was listed by the with arm in 2 of 3 control runs and by the
without arm in the third, so the check failed at random.
Checks
make test-evals: 75 tests pass. The newtest_quota_in_an_answer_is_not_infrafails with therun.pychangereverted, and the added
cross_arm_problemsassertion fails withthat change reverted.
Summary by CodeRabbit
MCP:cursoris no longer reported as an extra item in comparisons between evaluation arms.