Track disparity history and gate benchmark regressions - #329
Merged
Merged
Conversation
godofecht
force-pushed
the
feat/disparity-history-regression
branch
from
August 17, 2026 11:09
8f62f43 to
2fff3f3
Compare
godofecht
marked this pull request as ready for review
August 17, 2026 12:07
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.
Addresses #208.
Adds a persistent disparity-regression policy and history, compares each canonical rerun against the previous frozen disparity report, and fails CI on unexplained numerical/configuration/semantic regressions. Pages now publishes disparity history alongside the existing data-driven runtime and disparity plots while preserving the direct MLIR WebAssembly deployment path.
The branch is based on current main and intentionally excludes generated benchmark/architecture snapshots; CI remains responsible for freezing validated evidence.