This issue is hitting us every second day now. Since we didn't have this before using a 5.0 wrapper, I consider it a regression.
I therefore assigned it to 5.0 RC1.
@ghale I assigned you to fix it for RC1, do you think that is feasible? Or do I need to find someone else?
I don't consider this a regression - this problem has been around for a while. We've just been triggering it more recently - perhaps because Groovy daemons are dying more frequently? We should probably get someone to take a look at what's going on there as that's likely the real regression.
Regardless, I've got a fix for the worker daemon manager issue mostly implemented, so I'll finish it up and try to get it into 5.0.
ghale
commented
5 years ago
@blindpirate commented on Thu Sep 13 2018
MESSAGE: finished with non-zero exit value 255
https://builds.gradle.org/viewLog.html?buildId=15728996&buildTypeId=Gradle_Check_Parallel_Java8_Ibm_Linux_scala
@eriwen commented on Thu Sep 13 2018
09/12/2018 12:03:14 - https://builds.gradle.org/viewLog.html?buildId=15728996&buildTypeId=Gradle_Check_Parallel_Java8_Ibm_Linux_scala
@ghale commented on Tue Sep 25 2018
See discussion here on what needs to done to fix this.
@wolfs commented on Mon Oct 15 2018
This issue is hitting us every second day now. Since we didn't have this before using a 5.0 wrapper, I consider it a regression. I therefore assigned it to 5.0 RC1.
@ghale I assigned you to fix it for RC1, do you think that is feasible? Or do I need to find someone else?
@wolfs commented on Mon Oct 15 2018
See https://builds.gradle.org/viewLog.html?buildId=16640599&tab=buildResultsDiv&buildTypeId=Gradle_Check_CompileAll
@ghale commented on Mon Oct 15 2018
I don't consider this a regression - this problem has been around for a while. We've just been triggering it more recently - perhaps because Groovy daemons are dying more frequently? We should probably get someone to take a look at what's going on there as that's likely the real regression.
Regardless, I've got a fix for the worker daemon manager issue mostly implemented, so I'll finish it up and try to get it into 5.0.
@wolfs commented on Mon Oct 15 2018
@ghale Thank you! Any idea who could look into the Groovy daemons dying more frequently? Can this be related to the Groovy upgrade?
@ghale commented on Mon Oct 15 2018
Quite possibly. If I had to guess, I'd say it's probably the daemon running out of memory or something like that.