[
https://issues.apache.org/jira/browse/BEAM-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459505#comment-17459505
]
Kenneth Knowles commented on BEAM-13456:
----------------------------------------
We do see OOMs in the runs that don't time out. The other runs may be crash
looping and logging to local filesystem.
{code}
RuntimeError: org.apache.beam.sdk.util.UserCodeException:
java.lang.AssertionError: Count/ParMultiDo(Anonymous).output: Java heap space
at
org.apache.beam.sdk.util.UserCodeException.wrap(UserCodeException.java:39)
at
org.apache.beam.sdk.testing.PAssert$DefaultConcludeFn$DoFnInvoker.invokeProcessElement(Unknown
Source)
at
org.apache.beam.fn.harness.FnApiDoFnRunner.processElementForParDo(FnApiDoFnRunner.java:750)
{code}
I noticed in the caching PR this was a risk. We could configure more JVM heap
space, if it isn't already high.
> beam_PostCommit_Java consistently timing out.
> ---------------------------------------------
>
> Key: BEAM-13456
> URL: https://issues.apache.org/jira/browse/BEAM-13456
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Affects Versions: 2.36.0
> Reporter: Daniel Oliveira
> Assignee: Luke Cwik
> Priority: P1
> Labels: currently-failing
>
> This seems to have first appeared with build #8367:
> [https://ci-beam.apache.org/job/beam_PostCommit_Java/8367/]
> Frustratingly, no build scans pop up when the test fails this way, and no
> error messages appear except for the timeout. It may be easiest to attempt to
> determine which commit introduced the error.
> The previous successful test is at commit
> b52762bf150cacceb0fdeb1f0dc85cbea6e6f39c
> The first failing test is at commit 06a5e67332aae53ea90dedb4ef6421c2a7d65035
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
