-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BUG] Java Heap Space Causing Gradle Check Failures #4907
Comments
This is interesting, suppossed to be fixed by #3973 but ... Gradle cache?
|
We haven't merged from main in a little bit, will see if #4916 resolves this |
Thank you for the response. Apologies if I missed this or we are behind with our merges. I just wanted to raise it to your attention in case it was a persistent issue that was not on people's radar. We will keep you updated. |
@scrawfor99 Can you rebase and see if this issue is resolved? |
Closing this as it seems to have been fixed. @scrawfor99 Please re-open if you still hit this issue. |
When testing a change to the feature/identity repo, I encountered an issue with the gradle check Jenkins process. After the check running for 17 minutes, the build fails with approximately 30 instances of the failure "Java heap space" presumably relating to the heap memory allocation.
Full logs can be found here: https://build.ci.opensearch.org/job/gradle-check/5471/console
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The check passes (or doesn't) regardless of memory allocation.
Screenshots
Here is a screenshot of the bottom part of the gradle-check console:
The text was updated successfully, but these errors were encountered: