From 4c803ff700e23f57b8486a323246bbeccf7d5807 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gregor=20Jer=C5=A1e?= Date: Thu, 11 Jul 2024 08:50:51 +0200 Subject: [PATCH] Use NULL_EXECUTOR when running e2e tests --- .github/workflows/e2e.yaml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/.github/workflows/e2e.yaml b/.github/workflows/e2e.yaml index c419f384..0dc8ae42 100644 --- a/.github/workflows/e2e.yaml +++ b/.github/workflows/e2e.yaml @@ -105,8 +105,28 @@ jobs: - name: Try the cluster run: | - kubectl wait --for=condition=available --timeout=1200s -n default deployment/postgres # Until postgres is fully restored, the services will fail + kubectl wait --for=condition=available --timeout=1200s -n default deployment/postgres + # Patch the channels manager to use the null executor + kubectl patch deployment channels-manager -n default --patch '{ + "spec": { + "template": { + "spec": { + "containers": [ + { + "name": "channels-manager", + "env": [ + { + "name": "GENESIS_EXECUTOR_NULL", + "value": "1" + } + ] + } + ] + } + } + } + }' # Perform a clean restart of all services after the database is online kubectl rollout restart deployment asgi-server channels-manager listener background-task uploader kubectl wait --for=condition=available --timeout=1200s --all deployments