Verify suite gates and JUnit offline in v0.8.0 - #8
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
1 participant
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.
A received suite previously required checking its repetitions individually; its original configuration, acceptance decisions and JUnit could not be verified by the installed CLI. Version 0.8.0 recomputes the whole suite from TOML, plan and every attempt, checking job inventory/order, runtime and seed alignment, configured gates, totals and JUnit failure/error records. No candidate paths are resolved and no candidate or grader runs.
--require-accepteddistinguishes configured acceptance from record consistency and full resolution. The evidence lab offers a deterministic ZIP containing the featured suite's 12 unchanged original input files. It verifies successfully while correctly reporting two accepted jobs and only one fully resolved job. Documentation explains exit codes, bounded reads and reported path/timing metadata; existing outreach is prepared for the released capability.Validation: full pre-download suite 253 tests, then 98 targeted verifier/suite/site tests including ZIP roundtrip and corruption cases; ruff; wheel and sdist build; installed wheel outside the checkout with empty PATH, including modified-JUnit rejection. Site and dataset builds plus desktop/mobile browser download checks. CI runs the full final suite on Python 3.11–3.13 and four task/language Docker audits before Pages/HF publication.