Repository navigation
observer-regression: a CI gate over dataset runs - #54
Merged
Merged
Conversation
Records a run from a results file (case -> trace) or gates a stored one, compares it with a baseline run and exits 0 (passes), 1 (regression or threshold failure) or 2 (could not decide). Unknown cases are reported apart and a run where nothing could be verified fails unless --allow-unverified, so the gate never goes green on no evidence. Roadmap step 4 marked done.
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.
Step 4 of docs/roadmap.md.
observer-regression(app/ops/regression_gate.py, entry point inbackend/pyproject.toml). Observer still does not execute the agent: CI passes the traces its cases produced (--results, case identified by its source trace or item id) or gates a stored run (--candidate latest).observer.regression.v1report), 2 could not decide (unreachable, unknown dataset/run, bad args).--max-regressions(default 0) block; without one, any failed case blocks (--max-failures). Optional--min-pass-rate,--max-health-drop,--fail-on-unknown.--allow-unverified: a gate must not go green on no evidence.previous, re-gate latest), error paths, exit code 2. Backend 194 passed, ruff clean. No dashboard or migration changes.Limitation (roadmap): tool/text expectations come back unknown on real traces until Manitos exports tool spans and reply text, so today the gate effectively enforces health conditions.