[
https://issues.apache.org/jira/browse/BEAM-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16972613#comment-16972613
]
Tomo Suzuki commented on BEAM-6435:
-----------------------------------
I observe this failure frequently in Apache Beam Jenkins. Are they caused by
the same reason?
[https://builds.apache.org/job/beam_PostCommit_Java_PVR_Spark_Batch/1271/console]
> beam_PostCommit_Java_PVR_Flink_Batch regularly failing
> ------------------------------------------------------
>
> Key: BEAM-6435
> URL: https://issues.apache.org/jira/browse/BEAM-6435
> Project: Beam
> Issue Type: New Feature
> Components: runner-flink, test-failures
> Reporter: Robert Bradshaw
> Assignee: Maximilian Michels
> Priority: Major
> Fix For: Not applicable
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Often there are no test failures, but the task fails with
> 11:02:59 Execution failed for task
> ':beam-runners-flink_2.11-job-server:validatesPortableRunnerBatch'.
> 11:02:59 > Process 'Gradle Test Executor 2' finished with non-zero exit value
> 137
> 11:02:59 This problem might be caused by incorrect test process
> configuration.
> 11:02:59 Please refer to the test execution section in the user guide at
> https://docs.gradle.org/4.10.3/userguide/java_plugin.html#sec:test_execution
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
