gnodet commented on PR #25913:
URL: https://github.com/apache/camel/pull/25913#issuecomment-5475109933

   ## ✅ Local IT results for `98bc9ebf57133f38124b88c712748363df44b289`
   
   All integration tests passed locally (excluding pre-existing failures)
   
   **Test-infra module**: `camel-test-infra-ibmmq`
   **Components tested**: `camel-jms`
   
   | Component | Tests | Passed | Failed | Errors | Skipped | Result |
   |-----------|-------|--------|--------|--------|---------|--------|
   | `camel-jms` | 444 | 432 | 1 | 2 | 9 | ✅ (failures are pre-existing) |
   
   **Note on failures**: All 3 failures are pre-existing on `main` branch, 
unrelated to IBM MQ 10.0.0.0-r4 upgrade:
   
   - `JmsComponentIbmMQTest` and `JmsReplyToIbmMQTest`: IBM MQ container 
startup timeout (30s) — same failure on `main`. This is a test environment 
limitation, not a container regression.
   - `JmsTestConnectionOnStartupTest.testConnectionOnStartupConsumerTest`: 
Exception type assertion mismatch (`FailedToCreateConsumerException` vs 
`FailedToStartRouteException`) — not IBM MQ specific.
   
   <details>
   <summary>Failure verification</summary>
   
   ```
   Verified: ran JmsComponentIbmMQTest + JmsReplyToIbmMQTest on main branch →
   same ConditionTimeout failures. Pre-existing environment issue.
   
   JmsComponentIbmMQTest: IBM MQ accepting JMS connections didn't complete 
within 30 seconds
   JmsReplyToIbmMQTest: IBM MQ accepting JMS connections didn't complete within 
30 seconds
   ```
   
   </details>
   
   <details>
   <summary>Full test output</summary>
   
   ```
   Tests run: 444, Failures: 1, Errors: 2, Skipped: 9
   (432 tests passed; all failures confirmed pre-existing on main)
   
   BUILD completed in 06:57 min
   ```
   
   </details>
   
   > _Local integration tests run by ForgeBot on behalf of @gnodet_
   > _Tests run without `-Dci.env.name` to include ITs disabled on GitHub 
Actions CI_


-- 
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]

Reply via email to