Fixing undeterministic behavior in shouldApplyConnectTimeoutPerRoute() test

Signed-off-by: Rodolfo Juarez <[email protected]>

Author: rjuare8

spring-cloud-gateway-server-webflux/src/test/java/org/springframework/cloud/gateway/filter/NettyRoutingFilterIntegrationTests.java

@@ -40,7 +40,6 @@
 
 import static org.assertj.core.api.Assertions.assertThat;
 import static org.assertj.core.api.Assertions.assertThatThrownBy;
-import static org.assertj.core.data.Offset.offset;
 import static org.hamcrest.Matchers.containsString;
 import static org.springframework.boot.test.context.SpringBootTest.WebEnvironment.RANDOM_PORT;
 
@@ -133,7 +132,8 @@ public void shouldApplyConnectTimeoutPerRoute() {
 
 		// default connect timeout is 45 sec, this test verifies that it is possible to
 		// reduce timeout via config
-		assertThat(System.currentTimeMillis() - currentTimeMillisBeforeCall).isCloseTo(5, offset(100L));
+		long duration = System.currentTimeMillis() - currentTimeMillisBeforeCall;
+		assertThat(duration).isLessThan(5000L);
 	}
 
 	@Test