davsclaus commented on PR #24592:
URL: https://github.com/apache/camel/pull/24592#issuecomment-4938275768
The camel-lumberjack test failure is a pre-existing flaky test, unrelated
to PR 24592.
Key evidence:
1. PR 24592 did not touch any camel-lumberjack files. The PR ("Mark
sensitive component options as secret and tag insecure SSL flags") only
modified annotation metadata in components like geocoder,
huggingface, openai, servicenow, smpp, twitter, vertx-http, weather,
whatsapp, wordpress, and catalog JSON files.
2. Lumberjack tests have a long history of flakiness — the git log shows:
- CAMEL-21438: Disable LumberjackDisconnectionTest on s390x — already
disabled on some platforms
- @Isolated annotation on all tests — they can't run in parallel
- DisabledOnOs(value = { OS.LINUX }, architectures = { "s390x" }) on the
disconnection test
3. The tests are network-based (Netty TCP server/client with port-0
binding) and timing-sensitive — LumberjackDisconnectionTest expects exactly 3
messages before an error-induced disconnect, and
LumberjackComponentSSLTest expects exactly 60 messages over SSL. Both
patterns are inherently racy on CI runners under load.
The CI also has surefire.rerunFailingTestsCount=2 configured, so this test
failed all 3 attempts (original + 2 reruns), suggesting a reproducible failure
on that particular CI runner — likely a port/timing
issue under the specific load conditions of that run.
Bottom line: Safe to re-run CI. The failure has nothing to do with the
PR's changes.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
