Michael Luckey created BEAM-6698:
------------------------------------
Summary: Portable Validates Runner Tests on Flink flaky after
update to gradle5
Key: BEAM-6698
URL: https://issues.apache.org/jira/browse/BEAM-6698
Project: Beam
Issue Type: Bug
Components: test-failures
Reporter: Michael Luckey
Assignee: Michael Luckey
After upgrade to gradle 5 [1], the two portable runner test projects on jenkins
- beam_PostCommit_Java_PVR_Flink_Streaming [2]
- beam_PostCommit_Java_PVR_Flink_Batch [3]
became flaky.
First investigation seems to point the tests to be failing on direct buffer
memory (e.g. [4]).
Although I am unsure, whether this is really the root cause, or something that
shows up after some other failure.
{noformat}
INFO: Transport failed
org.apache.beam.vendor.grpc.v1p13p1.io.netty.util.internal.OutOfDirectMemoryError:
failed to allocate 16777216 byte(s) of direct memory (used: 1895825695, max:
1908932608)
{noformat}
As far as I know, we do not set `-XX:MaxDirectMemorySize` anywhere in our
setup, neither does gradle itself. At least on my machine both gradle 4 and
gradle 5 stick to the same jvm default
{noformat}
###########################################
sun.misc.VM.maxDirectMemory(): 1908932608 Bytes
sun.misc.VM.maxDirectMemory(): 1820 MB
###########################################
{noformat}
[1] https://issues.apache.org/jira/browse/BEAM-6630
[2] https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Streaming/
[3] https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Batch/
[4] https://scans.gradle.com/s/tpo3yffjznfxa/tests/yobvrae4rwsg4-go44ti5iq45vq
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
