Give cellular migration fixture unique commit ID
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 2m10s
Foundation / checks (tsan) (push) Successful in 9m14s
Foundation / checks (postgres) (push) Failing after 32m32s
Foundation / checks (checks) (push) Successful in 38m28s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
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 2m10s
Foundation / checks (tsan) (push) Successful in 9m14s
Foundation / checks (postgres) (push) Failing after 32m32s
Foundation / checks (checks) (push) Successful in 38m28s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
This commit is contained in:
@@ -7064,3 +7064,10 @@ fixture: both used world 9755 in the same disposable database, so the existing
|
||||
region lease rejected the second provisioning call. The migration fixture now
|
||||
uses its own world id (9759). PostgreSQL integration remains CI-only here; the
|
||||
next push must validate this isolation fix and continue to the Harbor image job.
|
||||
|
||||
CI run #324 passed that region-lease setup, then found the fixture's genesis
|
||||
commit ID also collided with an existing region-lease test: commit IDs are
|
||||
unique across the database, and that fixture uses sixteen `0x50` bytes. The
|
||||
cellular migration genesis ID now has a distinct first byte while preserving
|
||||
the remaining test pattern. CI must rerun the PostgreSQL gate and downstream
|
||||
Harbor publish before a server image is available.
|
||||
|
||||
Reference in New Issue
Block a user