Repository navigation
refactor(benchmarks): group artifacts by benchmark family - #567
Merged
Merged
Conversation
aviggiano
marked this pull request as ready for review
August 13, 2026 14:25
Collaborator
Author
|
@aviggiano please review |
Closed
4 of 5 tasks
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
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
Verification
Closes #513
Greptile Summary
The PR reorganizes benchmark manifests, labels, history, and archived results under benchmark-family directories and updates their runtime, CLI, CI, documentation, and test consumers.
Confidence Score: 4/5
The PR is not yet safe to merge because cleanup and history publication for already-running pre-refactor candidates still fail on missing legacy policy paths.
The existing thread reply claims the cleanup path was fixed with a shared current-or-legacy resolver, but current HEAD hardcodes only family-scoped manifests in launch validation, publication preparation, and history scope validation, providing a concrete counterexample for legacy candidates.
Files Needing Attention: scripts/ci/validate-modal-benchmark-launch.mjs, scripts/ci/prepare-eval-history-publication.mjs, packages/evals/src/history.ts
Important Files Changed
Reviews (4): Last reviewed commit: "docs(evals): use canonical SCFuzzBench p..." | Re-trigger Greptile
Context used: