apupier opened a new pull request, #16054:
URL: https://github.com/apache/camel/pull/16054
The test is flaky on CI.
Locally, I was able to have it flaky locally with a delay of 3 milliseconds
(1 failure out of 100). It was previously 250 milliseconds delay. it seems to
not be always enough on Jenkins CI. Which is a bit weird as it is quite huge
gap.
Trying with a more important delay.
The order of received message is only based on this delay but if the second
route is not executing in this delay, the test is failing. There is no other
controls on that, there is no guarantee at Camel level to respect a specific
order.
# Description
it was causing this kind of error:
```
java.lang.AssertionError: Caught exception on mock://result due to:
expected: <BA> but was: <AB>
at
org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:2013)
at
org.apache.camel.component.mock.MockEndpoint.evalFailures(MockEndpoint.java:478)
at
org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:471)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:431)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:421)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:220)
at
org.apache.camel.ContextTestSupport.assertMockEndpointsSatisfied(ContextTestSupport.java:886)
at
org.apache.camel.processor.MulticastParallelStreamingTest.testMulticastParallel(MulticastParallelStreamingTest.java:56)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
at
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Caused by: org.opentest4j.AssertionFailedError: expected: <BA> but was: <AB>
at
org.apache.camel.processor.MulticastParallelStreamingTest$1.process(MulticastParallelStreamingTest.java:48)
at
org.apache.camel.component.mock.MockEndpoint.tryProcessing(MockEndpoint.java:1807)
at
org.apache.camel.component.mock.MockEndpoint.performAssertions(MockEndpoint.java:1799)
at
org.apache.camel.component.mock.MockEndpoint.onExchange(MockEndpoint.java:1722)
at
org.apache.camel.component.mock.MockEndpoint$1.process(MockEndpoint.java:309)
at
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:208)
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$SimpleTask.handleFirst(RedeliveryErrorHandler.java:440)
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$SimpleTask.run(RedeliveryErrorHandler.java:416)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.doRun(DefaultReactiveExecutor.java:199)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeReactiveWork(DefaultReactiveExecutor.java:189)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.tryExecuteReactiveWork(DefaultReactiveExecutor.java:166)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:148)
at
org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleSync(DefaultReactiveExecutor.java:64)
at
org.apache.camel.processor.MulticastProcessor.lambda$schedule$1(MulticastProcessor.java:389)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
```
# Target
- [ ] I checked that the commit is targeting the correct branch (note that
Camel 3 uses `camel-3.x`, whereas Camel 4 uses the `main` branch)
# Tracking
- [ ] If this is a large change, bug fix, or code improvement, I checked
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for
the change (usually before you start working on it).
<!--
# *Note*: trivial changes like, typos, minor documentation fixes and other
small items do not require a JIRA issue. In this case your pull request should
address just this issue, without pulling in other changes.
-->
# Apache Camel coding standards and style
- [ ] I checked that each commit in the pull request has a meaningful
subject line and body.
<!--
If you're unsure, you can format the pull request title like `[CAMEL-XXX]
Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the
appropriate JIRA issue.
-->
- [ ] I have run `mvn clean install -DskipTests` locally from root folder
and I have committed all auto-generated changes.
<!--
You can run the aforementioned command in your module so that the build
auto-formats your code. This will also be verified as part of the checks and
your PR may be rejected if if there are uncommited changes after running `mvn
clean install -DskipTests`.
You can learn more about the contribution guidelines at
https://github.com/apache/camel/blob/main/CONTRIBUTING.md
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
