Skip to content

0.11.3: a ledger is judged by a set that runs every case - #30

Merged
Sunrisepeak merged 2 commits into
mainfrom
gate-ledgers-full-set
Nov 21, 2026
Merged

Sunrisepeak merged 2 commits into
mainfrom
gate-ledgers-full-set

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

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 the pr tier, and its gate failed on every run whatever the change: the surface items that only the full tier's jobs use had no passing case in the group (mcpp run 44937152470).

  • 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 its failures and budgets and states in a note (notes in --json, note: in text) that it did not judge the ledgers. mtest report --sections ledgers writes their 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. Under mcpp 2026.11.21.1 both failed locally; this CI pins mcpp 2026.11.14.1, which does neither.
  • Docs (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.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant