gnodet opened a new pull request, #27597:
URL: https://github.com/apache/camel/pull/27597
## Summary
Fix the flaky `JmsComponentIbmMQTest` by extending the IBM MQ container
startup timeout from the default 60 seconds to 3 minutes.
## Root Cause
The IBM MQ container image was upgraded from 9.x to
`icr.io/ibm-messaging/mq:10.0.0.0-r4` (commit 9f3ff2e80894). The 10.0 image is
heavier and occasionally exceeds the default Testcontainers
`Wait.forListeningPort()` 60-second startup timeout on resource-constrained CI
nodes, causing:
```
ContainerLaunchException: Timed out waiting for container port to open
(localhost ports: [45267, 45268] should be listening)
```
The test has been flaky 125 times and failed once since August 24th; it was
never flaky before the image upgrade.
## Fix
Add `.withStartupTimeout(Duration.ofMinutes(3L))` to the `WaitAllStrategy`
in `IbmMQLocalContainerInfraService`, consistent with other heavy containers in
the Camel test-infra codebase:
- `camel-test-infra-fhir` — 3 minutes
- `camel-test-infra-keycloak` — 3 minutes
- `camel-test-infra-neo4j` — 3 minutes
- `camel-test-infra-milvus` — 3 minutes
- `camel-test-infra-pinecone` — 3 minutes
## Tests
The existing `JmsComponentIbmMQTest` provides the regression coverage. The
fix gives the container enough time to start on slow CI nodes, eliminating the
timeout-induced flakiness.
Fixes https://issues.apache.org/jira/browse/CAMEL-25234
---
_Hermes Agent (Claude Sonnet 4.6) on behalf of Guillaume Nodet_
--
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]
