Skip to content

regression evals #583

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Mar 15, 2025
Merged

regression evals #583

merged 8 commits into from
Mar 15, 2025

Conversation

seanmcguire12
Copy link
Member

why

  • combination evals take too long to run for small changes

Copy link

changeset-bot bot commented Mar 14, 2025

⚠️ No Changeset found

Latest commit: 1be2d27

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@seanmcguire12 seanmcguire12 merged commit 96fd035 into main Mar 15, 2025
15 checks passed
kamath pushed a commit that referenced this pull request Mar 25, 2025
* regressions

* combination needs regression

* separate regression jobs run in parallel

* fix experiment names, fix gh output

* set scores as gh outputs

* add label check for combo

* rm needs label guard for combos

* 2 trials per
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants