Skip to content

android build: Bump Gradle max memory use to 6 GiB #1361

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

gnprice
Copy link
Member

@gnprice gnprice commented Feb 16, 2025

Fixes, potentially, #1360.

Even after the bump to 4 GiB, CI is still occasionally flaking with a "Java heap space" error in the android suite:
https://github.com/zulip/zulip-flutter/actions/runs/13152142737/job/36817594452?pr=1327

So try bumping the memory limit still further. It's not entirely clear this will be enough (or that an even bigger number would be):
#1360 (comment)
but we'll find out.

@gnprice gnprice added the maintainer review PR ready for review by Zulip maintainers label Feb 16, 2025
Fixes, potentially, zulip#1360.

Even after the bump to 4 GiB, CI is still occasionally flaking
with a "Java heap space" error in the `android` suite:
  https://github.com/zulip/zulip-flutter/actions/runs/13152142737/job/36817594452?pr=1327

So try bumping the memory limit still further.  It's not entirely
clear this will be enough (or that an even bigger number would be):
  zulip#1360 (comment)
but we'll find out.
@gnprice
Copy link
Member Author

gnprice commented Feb 16, 2025

Turns out this apparent flake was actually just a classic bug in the GitHub web app:
#1360 (comment)

So we don't need this PR. (Or at least we don't yet have any indication that we need it.)

@gnprice gnprice closed this Feb 16, 2025
@gnprice gnprice deleted the pr-gradle-6g branch February 16, 2025 02:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintainer review PR ready for review by Zulip maintainers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant