Hey all, sorry if a bit OT.
I noticed yesterday th...
# gradled
Davide Giuseppe Farella
10/19/2022, 12:08 PMHey all, sorry if a bit OT.
I noticed yesterday the Gradle daemon is crashing on my GitHub Action while building an Android release.
Didn't do any major change, beside update AGP, Kotlin, Compose, etc, which were already pretty recent, so minor updates.
Am I the only one experiencing this?
solved 1
Davide Giuseppe Farella
10/19/2022, 12:10 PMFAILURE: Build failed with an exception.
* What went wrong: Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed) * Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.* Get more help at https://help.gradle.org
Task cinescoutcinescout-utilscinescout utils composemergeExtDexDebugAndroidTest
Task cinescoutcinescout-utilscinescout utils composecompileDebugAndroidTestKotlin##[error***Process completed with exit code 1.
t
tapchicoma
10/19/2022, 12:50 PMtry to limit workers count on CI
m
mbonnin
10/19/2022, 12:51 PMOr give your daemon overlord more RAM 😈
d
Davide Giuseppe Farella
10/19/2022, 12:53 PM@tapchicoma Could that be given by the parallelization of building many modules?
t
tapchicoma
10/19/2022, 12:53 PMyes
d
Davide Giuseppe Farella
10/19/2022, 12:54 PMMakes sense, I got like 50 🙂
org.gradle.workers.max=?
20?
Davide Giuseppe Farella
10/19/2022, 12:55 PMI see from doc:
Default is number of CPU processors.So should I limit to like 2? 🤔
t
tapchicoma
10/19/2022, 12:56 PMthe more parallel build - the faster it will finish, but will require more RAM. So check what Github agent has and tune accordingly
d
Davide Giuseppe Farella
10/19/2022, 12:56 PMMakes sense 🙂 Thank you
Davide Giuseppe Farella
10/20/2022, 12:35 PMI remembered I have 8GB of memory for JVM in my
gradle.properties3 Views