[
https://issues.apache.org/jira/browse/BEAM-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743181#comment-16743181
]
Maximilian Michels commented on BEAM-6435:
------------------------------------------
This is the same symptom we were seeing for parallel PreCommit test execution
where the FnHarness is used by multiple Flink clusters. My diagnosis so far is
that Jenkins is too memory constraints for multiple instances of the tests. I
will reduce the number of parallel tests to 1. With the new EMBEDDED
environment we cut down the execution time significantly, so that should be ok.
> 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: test-failures
> Reporter: Robert Bradshaw
> Assignee: Maximilian Michels
> Priority: Major
>
> 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
(v7.6.3#76005)
