omni migration

[sm745052]

Summary

Migrates integration tests from the legacy Cloud Spanner Emulator to Spanner Omni.

Changes

• CI/CD: Renamed .github/workflows/integration-tests-against-emulator.yaml to integration-tests-against-omni.yaml and updated it to use the Spanner Omni docker image (us-docker.pkg.dev/spanner-omni/images/spanner-omni:2026.r1-beta).
• Configuration: Changed default project and instance IDs to default to align with Spanner Omni's automatic default setup.
• Documentation: Updated README.md, docs/install.md, and docs/testing.md to provide instructions for Spanner Omni instead of the emulator.
• Tests:
  • Renamed helper function onlyRunForEmulatorTest to onlyRunForOmniTest across all integration test files.
  • Updated code comments referencing the emulator to reference Spanner Omni.
  • Increased concurrent workers in TestUpdateDDLForeignKeys from 1 to 5. (this was not possible in emulator)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 47.52%. Comparing base (ff062c6) to head (e82aa88).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1325   +/-   ##
=======================================
  Coverage   47.52%   47.52%           
=======================================
  Files         234      234           
  Lines       27098    27098           
  Branches      602      602           
=======================================
  Hits        12879    12879           
  Misses      13473    13473           
  Partials      746      746           

Components	Coverage Δ
backend-apis	42.98% <ø> (ø)
backend-library	51.87% <ø> (ø)
cli	24.10% <ø> (ø)
frontend	38.56% <ø> (ø)

Files with missing lines	Coverage Δ
cmd/import.go	86.93% <ø> (ø)
common/utils/utils.go	2.08% <ø> (ø)
sources/spanner/infoschema.go	5.20% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[rohitwali]

thanks for the changes Sandeep. Can you add some context on the changes and any broader intent behind it?

[sm745052]

thanks for the changes Sandeep. Can you add some context on the changes and any broader intent behind it?

@rohitwali i was trying to add a 5k tables integration test for schema migration and it turned out that the max number of tables for a db in spanner emulator is 2560.

Given that spanner omni was recently released and that might be more close to cloud spanner in its features / behaviour i was doing a POC if we can replace emulator with omni in our tests.