Fix unstability of CommandExecutorTest

1 files changed, 1 insertions, 3 deletions

diff --git a/sonar-plugin-api/src/test/java/org/sonar/api/utils/command/CommandExecutorTest.java b/sonar-plugin-api/src/test/java/org/sonar/api/utils/command/CommandExecutorTest.java
index e61f87c0e00..3c95ed9a8a5 100644
--- a/sonar-plugin-api/src/test/java/org/sonar/api/utils/command/CommandExecutorTest.java
+++ b/sonar-plugin-api/src/test/java/org/sonar/api/utils/command/CommandExecutorTest.java
@@ -135,9 +135,7 @@ public class CommandExecutorTest {
       // Future.get(), which is used by CommandExecutor, has not a precise timeout.
       // See http://stackoverflow.com/questions/23199820/future-get-timeout-precision-and-possible-alternatives
       // The deviation seems to be in both directions, so it implies to test something like >270ms instead of >300ms
-      assertThat(duration).as(e.getMessage())
-        .isGreaterThan(270L)
-        .isLessThan(400L);
+      assertThat(duration).as(e.getMessage()).isGreaterThan(270L);
     }
   }