From ce694ba2dae7aee58d94ac4bba4189a2691c6407 Mon Sep 17 00:00:00 2001 From: Rene Cannao Date: Tue, 5 May 2026 12:19:30 +0000 Subject: [PATCH] fix(ci): remove SKIP_CLUSTER_START=1 from mysql84-gr-g5 workflow The mysql84-gr-g5 group runs test_cluster1-t which requires a multi-node ProxySQL cluster (ports 6032, 26001-26009). With SKIP_CLUSTER_START=1 only the primary ProxySQL node starts, causing test_cluster1-t to fail with 'Can't connect to server on proxysql (115)'. --- .github/workflows/ci-mysql84-gr-g5.yml | 2 -- 1 file changed, 2 deletions(-) diff --git a/.github/workflows/ci-mysql84-gr-g5.yml b/.github/workflows/ci-mysql84-gr-g5.yml index 12fcac347..6b3ca8b95 100644 --- a/.github/workflows/ci-mysql84-gr-g5.yml +++ b/.github/workflows/ci-mysql84-gr-g5.yml @@ -85,7 +85,6 @@ jobs: cd proxysql export INFRA_ID="ci-mysql84-gr-g5" export TAP_GROUP="mysql84-gr-g5" - export SKIP_CLUSTER_START=1 test/infra/control/ensure-infras.bash - name: Run mysql84-gr-g5 tests @@ -93,7 +92,6 @@ jobs: cd proxysql export INFRA_ID="ci-mysql84-gr-g5" export TAP_GROUP="mysql84-gr-g5" - export SKIP_CLUSTER_START=1 test/infra/control/run-tests-isolated.bash - name: Cleanup