ammachado opened a new pull request, #23927: URL: https://github.com/apache/camel/pull/23927
# Description Fix three test reliability issues: **1. `DefaultConsumerBridgeErrorHandlerContinuedTest` (flaky assertion)** The test asserted `mock:result` would receive **zero** messages when `continued(true)` is set on the error handler. In practice, `continued(true)` causes the exchange to continue through the main route after error handling, so `mock:result` does receive at least one message. Changed the expectation to `expectedMinimumMessageCount(1)`. **2. `SimpleLRUCacheTest` (race condition after concurrent puts)** After the concurrent-put latch completed, the test immediately asserted cache size and eviction counter. The eviction listener callback can fire asynchronously, causing intermittent failures. Wrapped the post-latch assertions in `Awaitility.await().atMost(10, TimeUnit.SECONDS).untilAsserted(...)` so the assertions wait for the eviction to settle. **3. TensorFlow Serving test-infra: missing aarch64 image** The `bitnami/tensorflow-serving:2.18.0` image on Docker Hub is not available for `aarch64`. Replaced it with `mirror.gcr.io/bitnamilegacy/tensorflow-serving:2.19.1`, which is available on the Google mirror registry for that architecture, consistent with the project's preference for `mirror.gcr.io` over Docker Hub. # Target - [x] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [x] 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-21438) filed for the change (usually before you start working on it). # Apache Camel coding standards and style - [x] I checked that each commit in the pull request has a meaningful subject line and body. - [x] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes. --- _Claude Code on behalf of Adriano Machado_ -- 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]
