Claus Ibsen created CAMEL-24466:
-----------------------------------
Summary: Flaky test:
KafkaConsumerHealthCheckIT.testReadinessWhenDown fails with ConditionTimeout in
CI
Key: CAMEL-24466
URL: https://issues.apache.org/jira/browse/CAMEL-24466
Project: Camel
Issue Type: Bug
Components: camel-kafka
Reporter: Claus Ibsen
The integration test
org.apache.camel.component.kafka.integration.health.KafkaConsumerHealthCheckIT.testReadinessWhenDown
fails intermittently in CI with a ConditionTimeout error, unrelated to the
code changes in the triggering PR:
{noformat}
KafkaConsumerHealthCheckIT.testReadinessWhenDown:178 ยป ConditionTimeout
Assertion condition defined as a Lambda expression in
org.apache.camel.component.kafka.integration.health.KafkaConsumerHealthCheckIT
expected: <true> but was: <false> within 20 seconds.
{noformat}
The test failed on all 3 attempts (initial run + 2 reruns via
rerunFailingTestsCount=2), so the built-in retry mechanism did not mask it as
flaky in this instance.
Observed on:
* JDK 25 build, components/camel-kafka, failsafe integration-test phase
* Triggering PR: apache/camel#25551 (CAMEL-24337 - Add Python 3 language
component), which only touches
camel-python3/camel-language/camel-javascript/catalog and is unrelated to Kafka
- CI likely ran camel-kafka ITs because the PR touches core/camel-core-model,
triggering a broad "affected modules" test run.
* CI run:
https://github.com/apache/camel/actions/runs/32796932710/job/97650048195
Suggests the readiness health check (down-detection) timing assumption of 20
seconds is not reliably met in CI, causing flaky failures.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
