Complete M7.4b lineage checkpoint profile; M7.4 done
ADR-0062 adds a canonical LineageArchive codec (parents before children, organisms by id, FNV) that decodes by replaying admit/record_birth/ record_death and requires byte-identical re-encoding; it never overwrites an existing archive. LineageRegion binds the environmental producer and consumer accounts to archived organisms with identity high-waters, enforces closure (lifecycle vs deaths, exact living set, tick bounds) and records deaths in the tick that causes them. Checkpoint profile 2 (environmental-lineage-v1, history profile 1) publishes that container; schema v4 admits it with a 4,268,144-byte cap and requires each commit to keep its predecessor's profile, RNG, history and durability declarations. Linux adds provision/publish/recover for the profile on the shared publication path. Qualification found WSL2 stepping CLOCK_REALTIME back ~0.5 s every ~32 s, which made two 1 s-lease tests flaky under ASan. Tests now wait on database-time expiry; ADR-0060 records the slewed-clock requirement. Validated: Windows CTest 57/57; Linux GCC Debug/Release, clang-tidy and ASan/UBSan CTest 57/57 each; PostgreSQL suites 2x Release, 2x analysis, 5x ASan; SQL and C++ mutations each caught. No Docker/Gitea CI, remote store, process kill or deployment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -2158,3 +2158,58 @@ Only clean-to-v1 and exact-v1 restart are supported migration paths at this gate
|
||||
These are local socket and local disk only.
|
||||
- Not executed: Docker/Gitea CI, a remote object store or PVC, power-loss fsync
|
||||
semantics, read-back verification fault injection, process kill, and TSan.
|
||||
|
||||
## M7.4b lineage checkpoint profile - 2026-09-28
|
||||
|
||||
- Windows MSVC Release CTest passed 57/57, including the new `lineage-region-contracts`
|
||||
and extended lineage and region-checkpoint contracts. The repository clang-format
|
||||
19 check passed.
|
||||
- WSL Ubuntu (GCC 14.2.0, clang 19.1.1, PostgreSQL 18.6, OpenSSL 3.0.13):
|
||||
- The Linux `checks` build set (separate build dirs) passed CTest 57/57 in each
|
||||
of GCC14 Debug, GCC14 Release, clang19 analysis and clang19 ASan/UBSan.
|
||||
- The PostgreSQL integration suite passed 2× Release, 2× analysis and 5×
|
||||
ASan/UBSan.
|
||||
- Archive codec coverage:
|
||||
- canonical encoding regardless of admission order, including a child with a
|
||||
smaller ID than its parent;
|
||||
- checksum, magic, version, count cap, length and organism-count framing;
|
||||
- genome damage, unknown genome, invalid alive/died forms, death before birth,
|
||||
reordered organisms (non-canonical) and a child encoded before its parent;
|
||||
- a full 4096-genome/65536-organism round trip at 2,543,648 bytes.
|
||||
- `LineageRegion` coverage:
|
||||
- closure refusals: missing, identical or dead binding; low high-waters; stray
|
||||
living organism; future birth; archive death while the community is active;
|
||||
- the death recorded at tick 20 in the same advance; a refused tick changes
|
||||
nothing;
|
||||
- restore plus 36 continuation ticks identical to the original;
|
||||
- container, binding, envelope and archive damage refused.
|
||||
- Profile 2 coverage:
|
||||
- the 4,268,144-byte cap is asserted in C++ and enforced by SQL (the maximum is
|
||||
accepted, +1 refused); the profile-1 1 MiB+1 is refused;
|
||||
- mismatched profile/history is EVL06;
|
||||
- lineage publish (death included), recover and continue, and a second
|
||||
publication;
|
||||
- the environmental path refuses a lineage predecessor before upload;
|
||||
- the database refuses a profile switch;
|
||||
- a host of the other profile reports unsupported.
|
||||
- Migrations: clean→v4; v1→v4; v3 with a committed genesis upgraded to v4 with
|
||||
the commit retained; v2 heads still block. Tampered v2/v3/v4 checksums and an
|
||||
unknown v5 are refused.
|
||||
- Mutations (restored afterwards), each failing at the expected line: removing
|
||||
the SQL profile/history continuity check (store test 392), the living-set
|
||||
closure check (lineage region 58), or death recording (lineage region 78).
|
||||
- Flake found and fixed. The ASan PostgreSQL suite failed intermittently: 1 of 3,
|
||||
then 1 of 5 runs, at the queued-writer and expired-renewal assertions.
|
||||
- Cause: a 4-minute probe measured WSL2 stepping CLOCK_REALTIME back 470-596 ms
|
||||
every ~32 s (3.66 s total, roughly 1.5% versus CLOCK_MONOTONIC).
|
||||
- PostgreSQL `clock_timestamp()` follows that wall clock, so a 1.2 s local sleep
|
||||
could be under 1 s of database time.
|
||||
- Tests now poll `clock_timestamp() >= expires_at`, holding the row lock where
|
||||
relevant. Afterwards the suite ran 5/5 under ASan.
|
||||
- The fencing logic itself was unchanged; the requirement is recorded in
|
||||
ADR-0060.
|
||||
- Local measurements, Release:
|
||||
- manifest publish p50 0.72 ms and p99 1.24 ms;
|
||||
- checkpoint publication 3.5-5.0 ms for 23-37 KiB payloads.
|
||||
- Not executed: Docker/Gitea CI, remote storage, process kill, reproduction within
|
||||
a batch (the fixture has none), durable history rows (M7.5) and TSan.
|
||||
|
||||
Reference in New Issue
Block a user