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.

Sign up for GitHub

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

Jump to bottom

Graalvm nightly build failed due to insufficient memory #11377

Open
zhumin8 opened this issue Jan 6, 2025 · 0 comments
Open

Graalvm nightly build failed due to insufficient memory #11377

zhumin8 opened this issue Jan 6, 2025 · 0 comments
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@zhumin8
Copy link
Contributor

zhumin8 commented Jan 6, 2025

Graalvm nightly build failed for " Google Cloud Vertex AI 3.56.0" due to

# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 1630011392 bytes for committing reserved memory.

full log: https://fusion2.corp.google.com/invocations/ebe46b41-95d5-4e29-8959-c0f61bedb27e/targets/cloud-devrel%2Fclient-libraries%2Fjava%2Fgoogle-cloud-java%2Fnightly%2Fgraalvm-sub-jobs%2Fnative-a%2Fgraalvm-native-5;config=default/log

This may be flaky, rerunning job
@zhumin8 zhumin8 mentioned this issue Jan 8, 2025
Open
@diegomarquezp diegomarquezp added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zhumin8 @diegomarquezp