beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From m..@apache.org
Subject [beam] branch release-2.10.0 updated: [BEAM-6418] Execute Flink tests serially to avoid memory issues
Date Tue, 15 Jan 2019 16:41:16 GMT
This is an automated email from the ASF dual-hosted git repository.

mxm pushed a commit to branch release-2.10.0
in repository https://gitbox.apache.org/repos/asf/beam.git


The following commit(s) were added to refs/heads/release-2.10.0 by this push:
     new 6cd27b0  [BEAM-6418] Execute Flink tests serially to avoid memory issues
6cd27b0 is described below

commit 6cd27b0928f1cae2489fa9d6bcd18b3b76b7f56d
Author: Maximilian Michels <mxm@apache.org>
AuthorDate: Mon Jan 14 21:30:35 2019 -0500

    [BEAM-6418] Execute Flink tests serially to avoid memory issues
    
    We had previously disabled Flink tests for 1.6 and 1.7 due to memory issues when
    they executed in parallel. This lets them execute one after another.
---
 runners/flink/flink_runner.gradle | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/runners/flink/flink_runner.gradle b/runners/flink/flink_runner.gradle
index 51f2e3b..d90ef2c 100644
--- a/runners/flink/flink_runner.gradle
+++ b/runners/flink/flink_runner.gradle
@@ -68,6 +68,13 @@ test {
   if (System.getProperty("beamSurefireArgline")) {
     jvmArgs System.getProperty("beamSurefireArgline")
   }
+  // TODO Running tests of all Flink versions in parallel can be too harsh on Jenkins memory
+  // Run them serially for now, to avoid "Exit code 137", i.e. Jenkins host killing the Gradle
test process
+  if (project.name == "beam-runners-flink-1.6") {
+    dependsOn(":beam-runners-flink_2.11:test")
+  } else if (project.name == "beam-runners-flink-1.7") {
+    dependsOn(":beam-runners-flink-1.6:test")
+  }
 }
 
 configurations {


Mime
View raw message