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.
feat: read evals from usage artifact instead of dedicated evals artifact #45797
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
Uh oh!
There was an error while loading. Please reload this page.
feat: read evals from usage artifact instead of dedicated evals artifact #45797
Changes from all commits
61b6df1e671c994f967419c7756a7561ec59d43240File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] The
evalsandusagesets now resolve to the same artifact (constants.UsageArtifactName). There is no test asserting thatResolveArtifactFilter(["usage", "evals"])deduplicates to["usage"](a single download) rather than downloading the usage artifact twice. The deduplication likely happens further downstream, but it should be explicitly covered.💡 Suggested test
Add to
TestResolveArtifactFilter:{ name: "evals + usage deduplicates to single usage artifact download", sets: []string{"evals", "usage"}, expected: []string{"usage"}, },This guards against double-downloading if callers pass both sets.
@copilot please address this.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.