03Sheet 03.04 · Tools

Coverage

make coverage and make coverage-report: every XDR union arm reachable from LedgerCloseMeta is either reached by a corpus entry or classified with the stellar-core source line that decides it.

make coverage          # arms in the corpus bytes and the mined ledgers
make coverage-report   # COVERAGE.md: every arm reached by an entry, or classified; fails if any is neither
make coverage-goldens  # plus stellar-core's own golden ledgers (downloads about 76 MB once)

A walker reads the rs-stellar-xdr definitions for v30.0, and lists every union arm and enum member reachable from LedgerCloseMeta. It then walks real ledgers and records which arms they meet.

LedgersUnion arms
Reachable from LedgerCloseMeta499 (and 411 enum members)
Entry files (543 variant files: raw .xdr, alternate change orderings, and .xdr.zst decompressed)350 of 499
The mined ledgers (37 files)289 of 499
Entries and mined ledgers together350 of 499
stellar-core's goldens (866 files, 15,306 ledgers, commit f2b91947)254 of 499

The corpus rows are computed from the corpus at commit 128b16b, the same way make coverage computes them. The goldens row is a fixed measurement at stellar-core commit f2b91947. The goldens are the ledgers stellar-core's own tests produce.

Every arm accounted for

make coverage counts every arm in an entry's file, including arms from other transactions that happen to share its ledger. make coverage-report is stricter. An entry reaches an arm only when its own transaction (envelope, fee changes, apply meta) or its ledger's own shape (header, transaction-set phases, upgrades, evicted keys) contains it. Every arm no entry reaches is classified in coverage/exclusions.json, with the stellar-core source line that decides it. The run fails if an arm is in neither list, or in both.

Union arms reachable from LedgerCloseMetaArms
Reached by an entry: its own transaction, or its ledger's header and transaction-set shape350
todo: core can write it at protocol 30 and a standalone recipe can produce it; not yet in an entry67
network-only: reachable in closed ledgers, but only under live-network conditions a standalone core cannot set up; to be mined8
historical: only in ledgers of older protocols (range in the note)18
validation-only: set only where a transaction is validated for inclusion; a closed ledger never carries it at protocol 3039
not-emitted: in the type graph, but stellar-core 30 never writes it into ledger-close meta17
Total499

Enum members reached by an entry: 275 of 411. The report is written to COVERAGE.md, with the entries that target each hazard.

Only the 67 todo arms and the 8 network-only ones are work left for the corpus. A closed protocol-30 ledger never carries a validation-only or not-emitted arm, and a historical one appears only in ledgers of older protocols.

On this page