| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The corpora written from four seeds of each kind showed little: of 32 histories, 4
versions written, no move and no stop, and every merge event refused, as the generator
signed them with any of ten node keys, so the corpus of revision 1 judged as the base
revision's did.
A generated merge event is signed by a node its party lists there, more often than not.
Of each kind, the corpus keeps the histories of the first two seeds, and of the next 400
those showing what the ones kept don't (`shows`: of each kind of event, what became of
one; a version written, a move, a stop), eight at most. The check asks that together a
revision's cases show a version written, a move to a checkpoint, a stop, and a merge event
taken where the revision has merge events, else refused.
|
|
|
Nothing checked that judging under a revision stays what it was: a change to the fold
that alters what an earlier revision takes, refuses or reads parts nodes running it from
nodes that don't, and the tests regenerate their expectations with the code.
For each revision this continuum knows, a file in `src/federation/corpus/` holds
histories generated at that revision, of every kind the properties generate, each event's
bytes with what became of it, by kind and never by a refusal's words, and what the store
reads after; its first line names the revision by its ID. It is written once, as the
revision is made (`write_the_corpus`, an ignored test run by hand), and never edited
after; every later continuum judges it alike (`every_revision_judges_as_its_corpus_says`),
which fails where a revision has no corpus yet, saying how to write it.
The test plan describes it.
|