Repository navigation
ci(ai-evals): Run each label on several models in parallel - #373
Merged
Merged
Conversation
jaydgoss
marked this pull request as draft
October 19, 2026 20:59
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b6e31cd. Configure here.
jaydgoss
force-pushed
the
jaygoss/evals-on-several-models
branch
from
October 20, 2026 17:40
192e2fa to
32d687f
Compare
Each label runs once per agent model the harness's plan-evals action lists, one job and artifact per model. A report job per label and side downloads every model's artifact and uploads them as one run with the harness's report-evals action, so evals.sentry.dev's PR comment, which shows only a dataset's newest run, has every model.
Matches the eval repo's plan-evals output, a list of targets rather than of models, so a Codex target later is one more entry there.
The report job gathered each target's results through artifacts, which this public repo can't keep private. The plan job now creates one run per label and side on evals.sentry.dev with sentry-for-ai-evals' create-runs action, and each target's job sends its results into it.
jaydgoss
force-pushed
the
jaygoss/evals-on-several-models
branch
from
October 20, 2026 20:10
32d687f to
1763229
Compare
Sentry Evalssentry-for-ai-evals:sentry-get-started:products (Comparison)
|
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.
The sentry-for-ai-evals side of VDY-259 is getsentry/sentry-for-ai-evals#56. The matrix lives in this workflow, so it needs the target axis here too.
plan-evalsaction, so adding a model or a Codex target later needs no change here), one job per target.create-runsaction, and each target's job sends its results into it. Nothing passes between jobs but the run id, and no artifact of the outputs is kept, as in ci(ai-evals): Stop keeping eval outputs as artifacts #375.Merge getsentry/sentry-for-ai-evals#56 first; this checks that repo out at main. Rebased on main; #375 removes the same artifact line and can land in either order.
🤖 Generated with Claude Code