-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle build daemon disappeared unexpectedly #123
Comments
Did you try either running it without the daemon ( |
Hi I've been testing now and then for the last two days. I tweaked memory up, moved the runner to another way more beefy instance, tried multiple gradle daemon options like
No success. It's crashing very fast, that's the only improvement. |
I'm having the same issue. I found some indication here that there might not be a good way to keep the gradle daemon from running. Most of solutions I'm seeing involve upping the machine resources so it doesn't run out of memory, or increasing the heap size. |
@rgarrigue @mibzman Did you guys ever figure out, how to prevent this issue? |
Nope, never got it to work, and moved out of the job since then |
Thanks for your update. I'll keep this issue open then until we identified the root cause and a proper workaround to document. |
I encountered the same issues as described here on Gitlab today. I found out that I changed my display name on Gitlab with Emoji's in it. This causes the Gradle to result in an error as described here. So maybe this would help someone identify the same error. Check your display name in profile page or even check all the See next bug report: https://gitlab.com/gitlab-org/gitlab-ce/issues/48099 Even if your commit message has an unicode in it, it will break Gradle, see: https://gitlab.com/gitlab-org/gitlab-ce/issues/48099#note_82495926 |
I believe my solution was to not run the ionic build portion of my build in Gitlab cloud. I had a local server that I configured to only accept jobs with an |
We have a EDIT: |
Also see next Gradle issue on GitHub: gradle/gradle#3117 (comment) |
Hello there, I use GitLab CI and this docker image from beevelop. Since I branched my repo from "master" branch, I got some weird errors from the pipeline. I am able to build a release version of my app, but not the debug version - using "--prod release' flag. The debug (normal) build shows that failed because of "Gradle build daemon disappeared unexpectedly". |
Hi beevelop
I tried your docker on my workstation to build a ionic2 project. Everything went fine.
Then I created a Gitlab pipeline to do exactly the same thing for our CI/CD... and it fails with a "Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)". Tried to get more logs with --debug and --stacktrace, I had no better clue, tried to upgrade the CI's runner VM to 2cpu / 4go ram, not better. Does that ring a bell to you ?
Here's the build stage script
And here's the log
The text was updated successfully, but these errors were encountered: