Skip to content

Fix Materialize CI by removing deprecated MZ_EAT_MY_DATA flag#1302

Merged
mrigger merged 1 commit intomainfrom
fix-materialize-ci
Mar 26, 2026
Merged

Fix Materialize CI by removing deprecated MZ_EAT_MY_DATA flag#1302
mrigger merged 1 commit intomainfrom
fix-materialize-ci

Conversation

@mrigger
Copy link
Contributor

@mrigger mrigger commented Mar 26, 2026

MZ_EAT_MY_DATA=1 is a deprecated env var from old Materialize versions that triggered an initialization path running CockroachDB-style SQL (SET CLUSTER SETTING sql.stats.forecasts.enabled = false), which is no longer valid in the current Materialize architecture.

Also add a pg_isready health check to ensure Materialize is accepting connections before tests run.

MZ_EAT_MY_DATA=1 is a deprecated env var from old Materialize versions
that triggered an initialization path running CockroachDB-style SQL
(SET CLUSTER SETTING sql.stats.forecasts.enabled = false), which is no
longer valid in the current Materialize architecture.

Also add a pg_isready health check to ensure Materialize is accepting
connections before tests run.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mrigger mrigger merged commit 46813b5 into main Mar 26, 2026
16 of 26 checks passed
@mrigger mrigger deleted the fix-materialize-ci branch March 26, 2026 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant