This is an automated email from the ASF dual-hosted git repository.

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


The following commit(s) were added to refs/heads/master by this push:
     new 488de2d  [BEAM-6418] Execute Flink tests serially on Jenkins to avoid 
memory issues
     new fa96ded  Merge pull request #7510: [BEAM-6418] Re-enable Flink 1.6/1.7 
tests via serial execution
488de2d is described below

commit 488de2d8aae5968f432d2d84bc6c931a925f3e56
Author: Maximilian Michels <m...@apache.org>
AuthorDate: Mon Jan 14 21:30:35 2019 -0500

    [BEAM-6418] Execute Flink tests serially on Jenkins 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 on 
Jenkins.
---
 runners/flink/flink_runner.gradle | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/runners/flink/flink_runner.gradle 
b/runners/flink/flink_runner.gradle
index add6162..41d49f0 100644
--- a/runners/flink/flink_runner.gradle
+++ b/runners/flink/flink_runner.gradle
@@ -68,10 +68,14 @@ test {
   if (System.getProperty("beamSurefireArgline")) {
     jvmArgs System.getProperty("beamSurefireArgline")
   }
-}.onlyIf {
   // TODO Running tests of all Flink versions in parallel can be too harsh on 
Jenkins memory
-  // Skip 1.6/1.7 tests for now, to avoid "Exit code 137", i.e. Jenkins host 
killing the Gradle test process
-  project.name != "beam-runners-flink-1.6" && project.name != 
"beam-runners-flink-1.7"
+  // 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") {
+    mustRunAfter(":beam-runners-flink_2.11:test")
+  } else if (project.name == "beam-runners-flink-1.7") {
+    mustRunAfter(":beam-runners-flink_2.11:test")
+    mustRunAfter(":beam-runners-flink-1.6:test")
+  }
 }
 
 configurations {

Reply via email to