Add structured failure reasons to benchmark summary output#119
Merged
Conversation
Each failed task in results.jsonl now carries a failure_reasons list covering harness failures, missing task.finished status, missing expected text, activity mismatches, missing final UI dumps, and missing trajectories or trajectory summaries. summary.json also gains a top-level failures list so contributors can see why tasks failed without digging through task directories. Existing fields are unchanged. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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
results.jsonl/summary.jsonnow includes afailure_reasonslist with concise structured reasons: harness failed, assistant did not reporttask.finished, expected text missing, expected activity missing or different, final UI dump missing, trajectory missing, and trajectory summary missing.summary.jsongains a top-levelfailuresarray (task_id+failure_reasons) so contributors can see at a glance why tasks failed without inspecting task directories.openphone.agent_benchmark_result.v1fields are preserved; only additive fields were introduced.Test plan
./scripts/check.shpassesgit diff --checkcleanbash -n scripts/run-agent-benchmark.shsyntax checkfailuressummary block came out as expectedscripts/run-agent-benchmark.sh --task settings-apps-pageend-to-end run, since it requires a connected device/emulatorCloses #41
🤖 Generated with Claude Code