-
Bug
-
Resolution: Done
-
Major
-
28.0.0.Beta1
-
None
We are encountering frequent failures of some Rest Client tests in our environment . E.g.
org.eclipse.microprofile.rest.client.tck.timeout.TimeoutTest.testConnectTimeout org.eclipse.microprofile.rest.client.tck.timeout.TimeoutViaMPConfigWithConfigKeyTest.testReadTimeout
Expected exception of type class jakarta.ws.rs.ProcessingException but got org.testng.TestException: Expected exception of type class jakarta.ws.rs.ProcessingException but got java.lang.AssertionError: Elapsed time expected under 55000ms, but was 64697ms. expected [true] but found [false]
StackTrace is e.g.
Caused by: java.lang.AssertionError: Elapsed time expected under 55000ms, but was 64697ms. expected [true] but found [false] at deployment.TimeoutTest.war//org.testng.Assert.fail(Assert.java:99) at deployment.TimeoutTest.war//org.testng.Assert.failNotEquals(Assert.java:1037) at deployment.TimeoutTest.war//org.testng.Assert.assertTrue(Assert.java:45) at deployment.TimeoutTest.war//org.eclipse.microprofile.rest.client.tck.timeout.TimeoutTest.checkTimeElapsed(TimeoutTest.java:67) at deployment.TimeoutTest.war//org.eclipse.microprofile.rest.client.tck.timeout.TimeoutTestBase.testConnectTimeout(TimeoutTestBase.java:69) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)