From 8a920aceadca7c6a999eabc20799f612483fd507 Mon Sep 17 00:00:00 2001 From: QIU Date: Mon, 3 Aug 2026 10:49:59 +0000 Subject: [PATCH] build: revert gradle heap cap, keep CI builds unconstrained The 768m heap cap broke GitHub Actions (KSP OutOfMemoryError: Metaspace) because CI runners read the same gradle.properties. Restore -Xmx6g for CI; the 2GB local server should pass a one-off -Dorg.gradle.jvmargs instead. --- gradle.properties | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/gradle.properties b/gradle.properties index cecc6eda..6308f0e2 100644 --- a/gradle.properties +++ b/gradle.properties @@ -1,6 +1,5 @@ # Configure your build environment: http://www.gradle.org/docs/current/userguide/build_environment.html org.gradle.caching=true -# NOTE: lowered from -Xmx6g for the 2GB build server; heavy release builds run on GitHub Actions -org.gradle.jvmargs=-Xmx768m -XX:MaxMetaspaceSize=256m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8 -org.gradle.parallel=false -org.gradle.workers.max=1 +org.gradle.jvmargs=-Xmx6g -XX:MaxMetaspaceSize=1g -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8 +org.gradle.parallel=true +org.gradle.workers.max=4