Repository navigation
Add a FrontierHarness Eval adapter under contrib/frontierharness (ENG-4328) - #806
Merged
Merged
Conversation
…-4328) Lets the benchmark maintainers rerun anton on Runta from this repo at a pinned commit: Harbor and Pier agent classes, the install and run scripts their workflow calls, and the patch their cost script needs to read anton's usage.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
FrontierHarness Eval only lists a harness after its maintainers rerun it themselves on Runta, so they need to install anton and its benchmark adapter from a public repo. This adds that adapter under
contrib/frontierharness/: the Harbor and Pier agent classes, the install and run scripts their workflow calls, and a small patch for their cost script. The README has the exact commands.Nothing outside
contrib/changes, and the folder is not in the wheel or the test suite.Tested on local Docker: the same adapter ran all 30 benchmark tasks, and
run-task.shran end to end on a non-benchmark task. It has not run on Runta yet.