Fix: set GRADLE_OPTS to avoid causing OOM when upload artifacts #92
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
henteko
approved these changes
Aug 1, 2024
Member
henteko
left a comment
henteko
left a comment
There was a problem hiding this comment.
I have confirmed that it is the same as here!
LGTM!
Member
Author
|
Thank you for your quick reaction and review! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Workflow of
Release artifactswas failed withjava.lang.OutOfMemoryError: Metaspace.But the workflow of
Build and test projectswas successful.Build and test projectshasGRADLE_OPTSenv and defined max size of Java heap memory and metaspace for the gradle deamon.So, I think we can fix this by setting
GRADLE_OPTSin your workflow file.