Skip to content

Record a failed Bug-origin session instead of ending Scoring - #1332

Merged
JacobStephens2 merged 1 commit into
mainfrom
scoring-origin-session-failure
Oct 25, 2026
Merged

JacobStephens2 merged 1 commit into
mainfrom
scoring-origin-session-failure

Conversation

@JacobStephens2

Copy link
Copy Markdown
Owner

The first Scoring run on the thirdshift host (#1032) failed after 13 minutes with Bug-origin session failed: Bug-origin proposal session failed; see private Grader artifacts, and no window was saved.

Why:

  • The first run backfills a Bug-origin proposal for every closed bug. For JacobStephens2 that's 113 bugs, each getting a session of up to 5 minutes.
  • Any one session failing ended the whole run.
  • The staged packets directory was dropped on that failure. It held packets/origins/<n>/ with the failed session's stderr and stdout.jsonl, so the "private Grader artifacts" the error pointed to no longer existed.
  • A retry repeats every session and can fail the same way.

Change:

  • A Bug-origin session that fails, times out or leaves no proposal now records that bug with no commit and a reason naming the failure.
  • The window keeps every other proposal and publishes the failed session's artifacts with them.
  • The Day shift settles that bug by hand, with --correct or --none.
  • Plan-limit stops, interrupts, a symlinked proposal and a commit outside the fix's history still advance no window, as before.

docs/guide.md, the generated site/docs/ and site/architecture/ say so.

Tests: tests/bug_origins.rs has a new test, a_failed_session_records_no_commit_keeps_its_artifacts_and_the_window_advances. It failed before this change (exit 1, no window) and passes now. All Bug-origin tests pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LSAzXiA6BD9neiPgVQRMKD

The first Scoring run backfills every closed bug, one session each. One
failed session ended the whole run with no window, and the staged
packets holding its artifacts were deleted, so the cause was lost and a
retry repeated every session. A session that fails, times out or leaves
no proposal now records that bug with no commit and says why; the window
keeps the other proposals and publishes the failed session's artifacts.
Plan-limit stops, interrupts and tampered proposals still advance no
window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LSAzXiA6BD9neiPgVQRMKD
@JacobStephens2 JacobStephens2 added the test:macos On a PR into main: run the full 4-shard macOS suite instead of the one-job macOS gate (#893) label Oct 25, 2026
@JacobStephens2
JacobStephens2 merged commit be63c34 into main Oct 25, 2026
21 of 28 checks passed
@JacobStephens2
JacobStephens2 deleted the scoring-origin-session-failure branch October 25, 2026 15:46
@JacobStephens2 JacobStephens2 mentioned this pull request Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test:macos On a PR into main: run the full 4-shard macOS suite instead of the one-job macOS gate (#893)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant