From 0508ea9de538da32f911c482ebdba2119676a23d Mon Sep 17 00:00:00 2001 From: Jean-Luc Makiola Date: Mon, 8 Jun 2026 16:53:30 +0200 Subject: [PATCH] fix(ci): split release.yaml sanity gradle calls to avoid OOM The release workflow's ci-sanity job ran 'lint test assembleDebug' as a single gradle invocation, which combined all three phases in one JVM and exceeded the 2GB heap inside the gitea-actions docker container ("Gradle build daemon disappeared unexpectedly"). Split into three separate invocations matching ci.yaml - each gradle call gets its own fresh 2GB JVM, well under the container's memory ceiling. Co-Authored-By: Claude Opus 4.7 (1M context) --- .gitea/workflows/release.yaml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/release.yaml b/.gitea/workflows/release.yaml index b6a2cc1..cf679f6 100644 --- a/.gitea/workflows/release.yaml +++ b/.gitea/workflows/release.yaml @@ -37,8 +37,14 @@ jobs: - name: Grant execute permission for gradlew run: chmod +x ./gradlew - - name: Lint + tests + debug build (sanity) - run: ./gradlew lint test assembleDebug --no-daemon + - name: Lint + run: ./gradlew lint --no-daemon + + - name: Unit tests + run: ./gradlew test --no-daemon + + - name: Assemble debug APK (sanity) + run: ./gradlew assembleDebug --no-daemon build-and-deploy: needs: ci