[codex] Refactor benchmark execution orchestration#53
Draft
glennmatlin wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
run_configexecution helpers.Why
The previous run path was hard to orchestrate safely for full benchmark runs: it mixed CLI-only behavior, prompt snapshot writes, API key attachment, output directory creation, and execution. The new runner gives us a repeat-aware, manifest-backed workflow that can dry-run plans, resume completed runs, and fail fast on partial or malformed outputs.
Validation
uv run ruff check src tests conftest.py scripts/run_benchmark.pyuv run pytest tests/-> 20 passed, 1 existing pydantic deprecation warningNotes
Generated benchmark outputs and quarantined partial runs remain local and are not included in this PR.