diff options
| author | tv <tv@krebsco.de> | 2026-11-19 12:46:42 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 13:52:29 +0100 |
| commit | 03105d40322dff9c18f0571872ab0f643aded0f7 (patch) | |
| tree | a96b625f4d57d23ee12a6db72780446530b413cd /src/api/health.rs | |
| parent | e8f0760a9b08e6b1a7372e79c48744035d1e4e1a (diff) | |
federation: checked against the release a federation-<F>.<R> tag namesfederation-1.1
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.
Diffstat (limited to 'src/api/health.rs')
0 files changed, 0 insertions, 0 deletions
