Fix Materialize CI by removing deprecated MZ_EAT_MY_DATA flag

mrigger · claude · mrigger · commit f2b42cef4fe1 · 2026-03-26T21:52:56.000+08:00
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 &lt;noreply@anthropic.com&gt;
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
@@ -392,7 +392,8 @@ jobs:
       - name: Set up Materialize
         run: |
           docker pull materialize/materialized:latest
-          docker run -e MZ_EAT_MY_DATA=1 -d -p6875:6875 -p6877:6877 materialize/materialized:latest
+          docker run -d -p6875:6875 -p6877:6877 materialize/materialized:latest
+          until pg_isready -h localhost -p 6875 -U materialize; do sleep 1; done
       - name: Set up JDK 11
         uses: actions/setup-java@v3
         with:
@@ -417,7 +418,8 @@ jobs:
       - name: Set up Materialize
         run: |
           docker pull materialize/materialized:latest
-          docker run -e MZ_EAT_MY_DATA=1 -d -p6875:6875 -p6877:6877 materialize/materialized:latest
+          docker run -d -p6875:6875 -p6877:6877 materialize/materialized:latest
+          until pg_isready -h localhost -p 6875 -U materialize; do sleep 1; done
       - name: Set up JDK 11
         uses: actions/setup-java@v3
         with:
