Fix cellular profile migration test fixture
Foundation / checks (client) (push) Successful in 6s
Foundation / checks (deploy) (push) Successful in 7s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 1m59s
Foundation / checks (tsan) (push) Successful in 8m54s
Foundation / checks (postgres) (push) Failing after 32m20s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 35m13s

This commit is contained in:
dingo
2026-10-12 00:34:56 -04:00
parent 2fee3b454e
commit a1439581d9
2 changed files with 33 additions and 10 deletions
+12
View File
@@ -7045,3 +7045,15 @@ post-publish assertion, so dependent image jobs remained blocked. The assertion
did not expose the sanitized database error category/SQLSTATE; the cellular host
publish result now carries those diagnostics to the test without server messages
or credentials. Validation of the diagnostic and migration 30 remains pending.
CI run #321 exposed the exact PostgreSQL error: PL/pgSQL's local record `b`
shadowed the `b` aliases in the duplicate-birth queries in migration 23. The
fix is a forward migration 31 so existing migration checksums remain intact.
Run #322 compiled the PostgreSQL targets and passed the earlier publication
test after migration 31, then exposed an obsolete test fixture that created a
non-empty profile-4 tick-0 genesis from a primitive life. ADR-0100 and ADR-0114
require empty genesis and allocator-backed births at a committed tick. The
fixture now creates empty legacy-v1 genesis, publishes its first life through
the normal control and birth path, then tests the v1-to-v2-to-v3 no-tick
migrations while carrying that living state. PostgreSQL integration cannot be
run in the local Windows environment, so this correction is awaiting CI.