[
https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845337#comment-17845337
]
Jang-Vijay Singh commented on CAMEL-20722:
------------------------------------------
I noticed you disabled these on s390x, but it probably wasn't necessary but
your call... Also that port conflict on CI that I mentioned earlier seems to be
gone in later builds.
I'm now running the camel-kafka & components builds repeated in multi-threaded
maven builds locally (both windows & Ubuntu VM).
So far, I have spotted a couple of tests that consistently succeeds in
single-threaded mode & fails regularly in multi-threaded mode. e.g.:
{code:java}
[ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 34.44 s
<<< FAILURE! -- in
org.apache.camel.component.kafka.integration.KafkaConsumerFullIT
[ERROR]
org.apache.camel.component.kafka.integration.KafkaConsumerFullIT.kafkaMessageIsConsumedByCamelAfterSuspendResume
-- Time elapsed: 20.63 s <<< FAILURE!
java.lang.AssertionError: mock://result Received message count. Expected: <5>
but was: <0>
at
org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1952){code}
> camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
> ---------------------------------------------------------------------------
>
> Key: CAMEL-20722
> URL: https://issues.apache.org/jira/browse/CAMEL-20722
> Project: Camel
> Issue Type: Task
> Components: camel-kafka
> Affects Versions: 4.4.1, 4.5.0
> Reporter: Otavio Rodolfo Piske
> Assignee: Jang-Vijay Singh
> Priority: Major
> Labels: help-wanted
> Fix For: 4.x
>
> Attachments: build-log.txt
>
>
> All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the
> CI. They fail often, sometimes in multiple archs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
