Update migration test for schema v17
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 1m53s
Foundation / checks (tsan) (push) Successful in 8m12s
Foundation / checks (checks) (push) Successful in 33m38s
Foundation / checks (postgres) (push) Failing after 34m18s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

This commit is contained in:
dingo
2026-10-10 17:34:18 -04:00
parent 2986c87f03
commit d9032253bd
2 changed files with 8 additions and 1 deletions
+7
View File
@@ -5719,3 +5719,10 @@ Windows clang-tidy 19.1.5 additionally reports `bugprone-exception-escape` on
the pre-existing PostgreSQL connection lambda in this test; this warning was not
present in the reported Linux CI diagnostics. The local tidy run excluded only
that check, so Linux CI remains authoritative for it.
The next PostgreSQL CI run passed analysis compilation and the publication tests,
then failed the online migration integration check because its expected schema
history stopped at v16. Updated that expectation through v17. clang-format 19.1.5
and `git diff --check` pass. This Linux-only test cannot compile in the Windows
shell because its process fixture requires `poll.h`; awaiting CI compile and
runtime confirmation.
+1 -1
View File
@@ -198,7 +198,7 @@ void upgrade_across_migration_and_barrier() {
CHECK(shell("PGDATABASE=" + database +
" EVO_PG_RUNTIME_ROLE=evo_runtime_test bash \"$EVO_SOURCE_ROOT/"
"tools/migrate-postgres.sh\" > /dev/null") == 0);
CHECK(history(*owner_db) == "1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16");
CHECK(history(*owner_db) == "1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17");
CHECK(renew_region_lease(*runtime, r.key, *lease, 20000ms, 5s));
confirm(publish_next(20)); // 41..60, now v8.
CHECK(head.head.end_tick == 60);