Page MenuHomePhabricator

[GH Actions] Add `gradle.jvmargs` args to `./gradlew bundleRelease`
ClosedPublic

Authored by atul on Aug 3 2023, 4:53 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Sep 26, 5:55 PM
Unknown Object (File)
Thu, Sep 26, 5:55 PM
Unknown Object (File)
Thu, Sep 26, 5:55 PM
Unknown Object (File)
Thu, Sep 26, 5:50 PM
Unknown Object (File)
Mon, Sep 23, 7:26 PM
Unknown Object (File)
Fri, Sep 20, 4:44 AM
Unknown Object (File)
Sat, Sep 14, 1:13 PM
Unknown Object (File)
Thu, Sep 12, 8:45 PM
Subscribers
None

Details

Summary

This is kind of a longshot, but noticed that the disk usage issue was accompanied by a stackoverflow issue during some sort of final signing step. This issue doesn't replicate on my fork because I didn't include the keys necessary for signing.

I also noticed that the disk usage issue specified that the error occured when trying to write to some sort of build log file.

Maybe there's a stack overflow issue that's causing a lot of logging that's eating up disk space? It's a stretch, but figure it doesn't hurt to bump gradle.jvmargs to possibly reduce chance of stack overflow?

Test Plan

Land and see what happens.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

atul published this revision for review.Aug 3 2023, 4:54 AM
atul added inline comments.
.github/workflows/android_ci.yml
55 ↗(On Diff #29506)

Without specifying values as command line args, will default to values specified in gradle.properties:

aede96.png (180×2 px, 73 KB)

(The Linux GH Actions runners have 7GB of RAM)

atul edited the summary of this revision. (Show Details)
This revision is now accepted and ready to land.Aug 3 2023, 5:07 AM