Skip to content

[LLM] Add Terminal-Bench evaluations and configurable CI - #23382

Closed
mergennachin wants to merge 1 commit into
mainfrom
llm/terminal-bench-evals
Closed

mergennachin wants to merge 1 commit into
mainfrom
llm/terminal-bench-evals

Conversation

@mergennachin

Copy link
Copy Markdown
Contributor

Add setup and run commands under examples/llm_server/evals so developers can evaluate exported models through the existing LLM server. Terminal-Bench is the first harness, with pinned Harbor/mini-SWE-agent versions and task subsets, model settings under evals/configs/, separate context and output budgets, and recorded task rewards, token usage, timings, trajectories, and verifier evidence.

Start review with evals/README.md and the example TOML, then terminal_bench/setup.sh and runner.py, followed by the CI workflow. Setup supports Ubuntu Docker Engine and macOS Colima; execution supports Docker Desktop too. Each trial owns a fresh server, with optional named-session affinity and resumable results. The periodic workflow uses configurable Linux GPU and macOS runners and stays disabled until LLM_SERVER_EVAL_TARGETS is provisioned.

Validation: 36 evaluation tests passed, including the current Python HTTP launcher with anonymous and named sessions using a fixture worker. Lintrunner, ShellCheck, Bash syntax checks, Actionlint, and the local prerequisite check passed. Earlier real Qwen3-0.6B trials reached the verifier but failed tool-call formatting; they provide integration evidence, not a task-quality baseline. This standalone revision has not run a new model evaluation or dispatched periodic CI.

Authored with assistance from OpenAI Codex.

Add setup and run commands under examples/llm_server/evals so developers can evaluate exported models through the existing LLM server. Terminal-Bench is the first harness, with pinned Harbor/mini-SWE-agent versions and task subsets, model settings under evals/configs/, separate context and output budgets, and recorded task rewards, token usage, timings, trajectories, and verifier evidence.

Start review with evals/README.md and the example TOML, then terminal_bench/setup.sh and runner.py, followed by the CI workflow. Setup supports Ubuntu Docker Engine and macOS Colima; execution supports Docker Desktop too. Each trial owns a fresh server, with optional named-session affinity and resumable results. The periodic workflow uses configurable Linux GPU and macOS runners and stays disabled until LLM_SERVER_EVAL_TARGETS is provisioned.

Validation: 36 evaluation tests passed, including the current Python HTTP launcher with anonymous and named sessions using a fixture worker. Lintrunner, ShellCheck, Bash syntax checks, Actionlint, and the local prerequisite check passed. Earlier real Qwen3-0.6B trials reached the verifier but failed tool-call formatting; they provide integration evidence, not a task-quality baseline. This standalone revision has not run a new model evaluation or dispatched periodic CI.

Authored with assistance from OpenAI Codex.
@pytorch-bot

pytorch-bot Bot commented Oct 3, 2026 •

Copy link
Copy Markdown

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/23382

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 146 Pending

As of commit c735eaa with merge base 0b3d26d (image):

NEW FAILURE - The following job has failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 3, 2026
@github-actions

github-actions Bot commented Oct 3, 2026

Copy link
Copy Markdown

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

This branch was successfully deployed

1 active deployment
cadence — c735eaa7 Deployed Oct 3, 2026 by mergennachin via hifi-op-test / hifi4 #31216
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant