[storm] branch master updated: STORM-3495 TestConstraintSolverStrategy is not stable on travis

[et...@apache.org]

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

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


The following commit(s) were added to refs/heads/master by this push:
     new 51ed4f8  STORM-3495 TestConstraintSolverStrategy is not stable on travis
     new dee4347  Merge pull request #3117 from dandsager1/STORM-3495
51ed4f8 is described below

commit 51ed4f89895213fb2521c0644b763c5db88fe9a5
Author: dandsager <da...@verizonmedia.com>
AuthorDate: Fri Aug 23 10:26:38 2019 -0500

    STORM-3495 TestConstraintSolverStrategy is not stable on travis
---
 .../resource/strategies/scheduling/TestConstraintSolverStrategy.java  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/storm-server/src/test/java/org/apache/storm/scheduler/resource/strategies/scheduling/TestConstraintSolverStrategy.java b/storm-server/src/test/java/org/apache/storm/scheduler/resource/strategies/scheduling/TestConstraintSolverStrategy.java
index 2235905..f43868d 100644
--- a/storm-server/src/test/java/org/apache/storm/scheduler/resource/strategies/scheduling/TestConstraintSolverStrategy.java
+++ b/storm-server/src/test/java/org/apache/storm/scheduler/resource/strategies/scheduling/TestConstraintSolverStrategy.java
@@ -210,7 +210,7 @@ public class TestConstraintSolverStrategy {
      * Cluster has sufficient resources for scheduling to succeed but can fail due to StackOverflowError.
      */
     @ParameterizedTest
-    @ValueSource(ints = {5, 20})
+    @ValueSource(ints = {1, 20})
     public void testScheduleLargeExecutorConstraintCount(int parallelismMultiplier) {
         // Add 1 topology with large number of executors and constraints. Too many can cause a java.lang.StackOverflowError
         Config config = createCSSClusterConfig(10, 10, 0, null);
@@ -238,7 +238,7 @@ public class TestConstraintSolverStrategy {
 
         boolean scheduleSuccess = isStatusSuccess(cluster.getStatus(topo.getId()));
 
-        if (parallelismMultiplier <= 5) {
+        if (parallelismMultiplier == 1) {
             Assert.assertTrue(scheduleSuccess);
         } else if (parallelismMultiplier == 20) {
             // For default JVM, scheduling currently fails due to StackOverflow.