Skip to content
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

Removes ci step modifying gradle.properties with extra jvmargs. #310

Merged
merged 1 commit into from
Aug 14, 2020

Conversation

Kritarie
Copy link
Contributor

Identical jvmargs are already defined in gradle.properties.

CircleCI is upset:

* What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the User Manual chapter on the daemon at https://docs.gradle.org/6.2/userguide/gradle_daemon.html
Process command line: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/bin/java -Xmx2048morg.gradle.jvmargs=-Xmx2g -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /Users/distiller/.gradle/wrapper/dists/gradle-6.2-bin/6zaomcc3lf3gnwxgkllci1muk/gradle-6.2/lib/gradle-launcher-6.2.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 6.2
Please read the following process output to find out more:
-----------------------
Invalid maximum heap size: -Xmx2048morg.gradle.jvmargs=-Xmx2g
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Identical jvmargs are already defined in gradle.properties.
@evant evant merged commit 5c615db into main Aug 14, 2020
@Kritarie Kritarie deleted the jvmargs-fix branch August 14, 2020 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants