Not a fix, but some insight. I've observed similar issues myself on large projects using gradle parallel mode. Disabling parallel mode on CI fixed the issue for me (
-Porg.gradle.parallel=false
).
Big Chungus
01/04/2022, 1:40 PM
Also make sure you have gradle daemon disabled on CI
s
simon.vergauwen
01/04/2022, 1:44 PM
It’s already using
parallel=false
.
Deamon is still enabled I think, I removed the argument because I saw Github Action automatically adding it but seems to be gone now.
Might’ve been a specific version of Gradle Action that was adding it.
Thanks for the tip, going to try running again with explicitly adding
-Dorg.gradle.daemon=false
🤞 4
p
Peter
01/04/2022, 5:41 PM
damn that sucks 😞 i’ve filed issues over there too, haven’t received any responses yet 😞
😔 1
s
simon.vergauwen
01/05/2022, 2:45 PM
Looks like it is going green with disabled daemon, and turned off