Repository navigation
Align names with task identifiers in eval harnesses - #7
Merged
Merged
Conversation
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.
Align catalogue eval names with harness task identifiers, and update the shipped eval sets, browser selectors, regression expectations, and YAML examples to use those names. Matching rules, metrics, normalization, language assignments, and weights are unchanged.
Contributors can run
python3 -m tests.checkbefore opening a PR. CI uses the same command: Python/JavaScript contract checks followed by the public browser suite in an automatically managed Chrome session. Missing browser prerequisites fail explicitly. Shared-engine coverage also validates the documented eval-set examples against the shipped catalogue.Validation:
test_analysis,test_app, andtest_english, reproduced on unchanged base commit8ec9540; this PR does not resolve those failures.Documentation: updated the configuration examples, README development command, contributor guidance, and development guide. PR builds validate and upload an artifact on success; only the separate main-branch deployment job publishes GitHub Pages.