gnodet commented on PR #25913: URL: https://github.com/apache/camel/pull/25913#issuecomment-5532195556
## Test results on Mac (M4 Max, Docker Desktop with QEMU x86_64 emulation) **`main` branch (IBM MQ `10.0.0.0-r3`):** - `JmsComponentIbmMQTest` — ✅ PASS (~30s) - `JmsReplyToIbmMQTest` — ✅ PASS (~30s) **With IBM MQ `10.0.0.0-r4`:** - `JmsComponentIbmMQTest` — ✅ PASS (3 consecutive runs, ~28-30s each) - `JmsReplyToIbmMQTest` — ✅ PASS (~30s) **Findings:** 1. Both tests pass reliably when the environment has enough resources — `r4` is fully compatible, no regression from `r3` 2. The previous failures on a lower-spec x86_64 machine were due to the **30s timeout in `waitForJmsConnection()`** being too tight — the IBM MQ container startup time varies with available resources 3. The tests are disabled on both GitHub Actions CI (`@DisabledIfSystemProperty`) and ARM64 (`@DisabledOnOs`), so they can only be exercised locally on x86_64 **Recommendation:** Increase the `waitForJmsConnection()` timeout from 30s to 60s in `IbmMQLocalContainerInfraService` — Awaitility exits as soon as the connection succeeds, so a higher cap doesn't slow down passing tests, it just prevents false failures on slower environments. -- 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]
