Details
-
Test
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.17.0
-
None
-
Unknown
Description
org.apache.camel.processor.ThrottlingExceptionRoutePolicyTest.testOpenCircuitToPreventMessageThree
java.lang.AssertionError: mock://result Expected minimum 500 millis waiting on the result, but was faster with 0 millis.
at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1824)
at org.apache.camel.component.mock.MockEndpoint.waitForCompleteLatch(MockEndpoint.java:1763)
at org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:447)
at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:427)
at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:417)
at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:214)
at org.apache.camel.ContextTestSupport.assertMockEndpointsSatisfied(ContextTestSupport.java:376)
at org.apache.camel.processor.ThrottlingExceptionRoutePolicyTest.testOpenCircuitToPreventMessageThree(ThrottlingExceptionRoutePolicyTest.java:100)
And then also 2 tests in camel-exec
https://ci-builds.apache.org/job/Camel/job/Apache%20Camel/job/main/245/testReport/
Attachments
Issue Links
- is related to
-
CAMEL-17948 Race condition in MockEndpoint with PER_CLASS tests
- Resolved