Repository navigation
report schema: state the evaluate verdicts and counts in the report - #316
Merged
Merged
Conversation
jar-ben
force-pushed
the
jaroslav/evaluation-summary
branch
from
November 18, 2026 12:51
0b7b5f0 to
442f3f4
Compare
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.
Problem
An evaluate report holds the raw facts (gap lists, run records, rule outcomes, property coverage)
but not the verdicts drawn from them. Every renderer derives them itself, and the derivations
differ.
Fix
The report states the verdicts, so a renderer only displays them:
ConfRunRecord.status:ran,build_failedorrun_failed.ConfCoverage.status:complete,incomplete,orphanedorunknown. It is about what theconfs select, not how their runs went;
unknownis a conf that did not build, so what it selectsis not known.
AutoProverReport.evaluation_summary: how many specs have each status, how many confs in scoperan or failed, how many rules have each outcome, and the two property axes (attempted, and the
faithfulness of the attempted ones).
All three are optional, so older reports load.
schema_version3.6.Testing
The evaluate-report round trip carries the new fields, and a report without them loads. The
non-expensive suite passes.