Repository navigation
0.11.3: a ledger is judged by a set that runs every case - #30
Merged
Merged
Conversation
A requirement is met by a passing case of the run's group, so a set that runs a part of the cases (`pr`, the cases a change affects) left unmet every requirement only the other cases meet, and its gate failed on every run whatever the change (mcpp's pull-request CI). `mtest gate` judges the ledgers for a set that runs every case (`full`, `release`, a declared set with `all`) and for a set it does not know; another set's gate judges the rest and states in a note (`notes`) that it did not judge them. The report writes the ledgers' table for any set. mtest's own tests hold under a runner that states its budget and serves run fixtures (mcpp 2026.11.21.1): the engine's runs under test state no outer budget, and the case that uses a fixture compares its endpoint with the one its runner stated.
This was referenced Nov 21, 2026
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.
A requirement of a ledger is met by a passing case of the run's group, so a set that runs a part of the cases (
pr, the cases a change affects) leaves unmet every requirement only the other cases meet. mcpp's pull-request CI runs theprtier, and its gate failed on every run whatever the change: the surface items that only thefulltier's jobs use had no passing case in the group (mcpp run 44937152470).mtest gatejudges the ledgers for a set that runs every case (full,release, a declared set withall) and for a set it does not know. Another set's gate judges its failures and budgets and states in a note (notesin--json,note:in text) that it did not judge the ledgers.mtest report --sections ledgerswrites their table for any set.commands.md,config.md,sets.md) and the CHANGELOG state the rule.0.11.3, source-compatible with 0.11.2; the library changes only the version it states.