android build: Allow gradle to use more memory #1324
Conversation
|
Looks like |
PIG208
force-pushed
the
pr-build
branch
2 times, most recently
from
2fc3919 to
38c283b
Compare
|
|
|
Will re-run this a few times to confirm that this succeeds continuously. |
|
This has been passing consistently. Still not too sure about the cause though. I suspect that flutter/flutter#162675 could be relevant. |
|
While the investigation to identify the cause is pending, let's merge this workaround first to fix the CI. |
gnprice
added
the
integration review
|
Thanks for doing these experiments! The commit message no longer seems accurate for what we know now: Given that it was such a steep change in the memory use, there's no longer any reason to think that we were near the old upper bound. I'll fix that, and also add some text as to why we're increasing the limit by so much, and also turn the chat link into a permalink: then merge. |
Fixes zulip#1330. Since Monday, CI builds have been running out of memory, presumably due to some upstream change. Allocate more memory so that the CI can pass again. The limit was 1.5 GiB, but now even 2.5 GiB doesn't seem to be enough. So increase it to 3 GiB. CZO discussion: https://chat.zulip.org/#narrow/channel/516-mobile-dev-help/topic/Execution.20failed.20for.20task.20'.3Aapp.3AcompileDebugKotlin'/near/2076887 Signed-off-by: Zixuan James Li <[email protected]>
|
Done. Also filed #1330 for the issue this fixes. |
Fixes #1330.
Recently, we have been running out of memory for the CI builds. It's likely that we were close to reaching the upperbound for some time, and some upstream change pushes us past that limit. Allocate more memory so that the CI can pass again.
CZO discussion:
https://chat.zulip.org/#narrow/channel/516-mobile-dev-help/topic/Execution.20failed.20for.20task.20'.3Aapp.3AcompileDebugKotlin'