Isolate cellular migration test world
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 2m2s
Foundation / checks (tsan) (push) Successful in 8m28s
Foundation / checks (postgres) (push) Failing after 32m52s
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 34m47s
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 2m2s
Foundation / checks (tsan) (push) Successful in 8m28s
Foundation / checks (postgres) (push) Failing after 32m52s
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 34m47s
This commit is contained in:
@@ -7057,3 +7057,10 @@ 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.
|
||||
|
||||
CI run #323 passed the normal build and reached the PostgreSQL integration
|
||||
suite, where the migration fixture collided with the primitive publication
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user