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
Java build flakes: "Memory constraints are impeding performance" #20819
Comments
I did not find a way, hence filed typetools/checker-framework/issues/5159 |
The folks at checkerframework are super responsive and their release process seems to take mere minutes, so if I get a review on typetools/checker-framework#5162 we should be able to move past this. Hopefully the increased heap size helps in the meantime. |
Still happen: https://ci-beam.apache.org/job/beam_PostCommit_Python38_PR/531/consoleText
|
:-( Re-running should help and once it is cached you will be clear of the problem. Otherwise we could split the memory across even fewer threads to allow a very large heap. In truth, it may not slow us down that much. We should primarily rely on caching for build performance. |
Still happening: https://ci-beam.apache.org/job/beam_PreCommit_Java_Examples_Dataflow_Commit/21203/console
|
Since checkerframework 3.26.0 this is something we can control. |
Freeing this up for anyone to take on since I'm doing other things right now. Good first issue since it doesn't require any context or judgment. |
Still happening: https://ci-beam.apache.org/job/beam_PreCommit_Spotless_Commit/23807/consoleFull
|
#24410 will enable us to fix this |
Java Wordcount Direct Runner (ubuntu-latest) failed a couple times on me with the following warning/error. It doesn't seem like "impeding performance" should cause the build to fail altogether, so I'm wondering if there's some way we can silence this warning.
Imported from Jira BEAM-11837. Original Jira may contain additional context.
Reported by: ibzib.
The text was updated successfully, but these errors were encountered: