diff --git a/docs/engineering/VALIDATION.md b/docs/engineering/VALIDATION.md index afddae1..5b63f04 100644 --- a/docs/engineering/VALIDATION.md +++ b/docs/engineering/VALIDATION.md @@ -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. diff --git a/tests/cellular_publication_tests.cpp b/tests/cellular_publication_tests.cpp index b74e6c0..5b407f6 100644 --- a/tests/cellular_publication_tests.cpp +++ b/tests/cellular_publication_tests.cpp @@ -217,8 +217,10 @@ void cellular_profile_migration_is_durable_and_recovers_without_a_tick() { auto objects = FilesystemObjectStore::open(env("PGHOST"), key, max_cellular_lives_bytes); CHECK(objects); + auto genesis_commit = filled<16>(0x50); + genesis_commit[0] = 0x51; auto provisioned = - provision_cellular_region(*owner, **objects, key, 1, **legacy, filled<16>(0x50), build, 5s); + provision_cellular_region(*owner, **objects, key, 1, **legacy, genesis_commit, build, 5s); CHECK(provisioned); CHECK(owner->query("INSERT INTO evolution.life_allocators VALUES(9759,1000) " "ON CONFLICT DO NOTHING",