Use valid cellular birth path in publication test
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (checks) (push) Failing after 4m12s
Foundation / checks (tsan) (push) Successful in 8m53s
Foundation / checks (postgres) (push) Failing after 32m37s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

This commit is contained in:
dingo
2026-10-12 04:10:38 -04:00
parent b51c96a576
commit d7b42f2be9
2 changed files with 27 additions and 14 deletions
+7
View File
@@ -7093,3 +7093,10 @@ on the newly created host; host recovery and lease acquisition happen during
`step()`. The test now checks readiness first, matching the established restart
test. PostgreSQL CI and Harbor image publication must rerun before a playtest
image is available.
CI run #328 passed that recovery check, then reached a second obsolete fixture
that constructed a tick-0 cellular genesis from a primitive life born at tick 1.
`CellularLives::create` correctly rejects that impossible chronology. The test
now provisions an empty v1 genesis and publishes its first life through the
allocator-backed control and birth path, retaining the action publication and
restart assertions. PostgreSQL CI and Harbor image publication remain pending.