| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A corpus of generated histories, committed, said what this code made of them, right or
not, and held hundreds of kilobytes a revision; generated from code that changes, it
could only be checked, never written again.
Each release that makes a revision is tagged `federation-<F>.<R>`, the federation's
number and the revision's (`federation-1.1`, revision 1 of federation 1).
`scripts/federation-check` writes histories from this tree (`write_histories`, an ignored
test): of each revision it knows and each kind the properties generate, those of a few
seeds from a random one it says, and the attack tests' crafted ones, as each test offered
them where nothing but offers made them. It judges them with `continuum-party judge` here
and with the continuum the latest such tag names (or one given), built in a worktree and
kept between runs, leaves out those whose root the tagged one reads as none, and says
where the two differ. Run before a release, not by `cargo quick`.
The corpus and its test are gone; the test plan and `federation.md` say how a release is
checked.
|
|
|
To check that a release judges histories as an earlier one did, under every revision
that one knows, each must say what its store makes of the same histories, in the same
words.
`continuum-party judge` reads histories from its input, each `case <label>`, `root
<hex>` and `event <hex>` for each event in the order offered, and prints for each what
became of every event by kind (`became <ID> <kind>`, never a refusal's words) and what
the store reads after (`reads <JSON>`): its checkpoint, the current version, the values
at places, the members, and the event it stopped at; `root none` where the root reads as
none, as one of a revision this continuum doesn't know (`federation::judge`). The format
is never to change: an earlier release prints it too.
|