ci: give analysis and QA enough memory - #389
Merged
Merged
Conversation
Up to standards ✅🟢 Issues
|
Member
|
@SystemKeeper how much RAM/memory do our -max worker have? |
|
14GB |
The analysis workflow wrote org.gradle.jvmargs=-Xmx1g into
~/.gradle/gradle.properties, which overrides the app's own
gradle.properties. lintGplayDebug then fails with "Java heap space",
and on push the wrapper still reports success without uploading a lint
baseline, so PR lint results are compared against a stale report.
Raise the heap to 6g and run analysis and QA on ubuntu-latest-max:
jobs landing on the smaller runners behind ubuntu-latest get killed
mid-build ("The runner has received a shutdown signal").
Verified on nextcloud/talk-android#6643, where lint now completes.
Assisted-by: Claude Code:claude-opus-5-5
Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
Signed-off-by: tobiasKaminsky <tobias@kaminsky.me>
Signed-off-by: tobiasKaminsky <tobias@kaminsky.me>
tobiasKaminsky
force-pushed
the
ci/analysis-heap-max-runner
branch
from
September 25, 2026 08:23
01a34e4 to
6270370
Compare
tobiasKaminsky
approved these changes
Sep 25, 2026
1 task done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The analysis workflow writes
org.gradle.jvmargs=-Xmx1ginto~/.gradle/gradle.properties, which overrides each app's owngradle.properties. On Talk,lintGplayDebugfails withJava heap space, and on push the wrapper still reports success without uploading a lint baseline (Talk'smaster.htmlhas not been updated since 2026-06-01), so PRs are compared against a stale report.Jobs on the plain
ubuntu-latestlabel also land on the smaller self-hosted runners, which get killed mid-build with "The runner has received a shutdown signal".Changes:
analysis.yml: heap-Xmx1g→-Xmx6g,runs-on: ubuntu-latest-maxqa.yml:runs-on: ubuntu-latest-maxVerified on nextcloud/talk-android#6643: lint now completes (Analysis there only fails on the stale baseline) and QA passes on
ubuntu-latest-max.🤖 AI (if applicable)