[
https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851360#comment-17851360
]
Jang-Vijay Singh commented on CAMEL-20722:
------------------------------------------
As a side effect of the proposed change here:
[https://github.com/apache/camel/pull/14298
|https://github.com/apache/camel/pull/14298] I expect the symptom observed till
build 96 to also go away.
I noticed that the root cause for why this test was originally so slow to
publish to partion 1 (compared to partition 0), was:
the required number of partitions were not fully created before they were being
used.
This pull request should address the root cause
> 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)
