Skip to content

chore(camel-test-infra-ibmmq): upgrade ibm.mq.container to 10.0.0.0-r4 - #25913

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
automated/upgrade-ibm-mq-container-10.0.0.0-r4
Open

chore(camel-test-infra-ibmmq): upgrade ibm.mq.container to 10.0.0.0-r4#25913
github-actions[bot] wants to merge 1 commit into
mainfrom
automated/upgrade-ibm-mq-container-10.0.0.0-r4

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This PR updates the ibm.mq.container container image to version 10.0.0.0-r4.

Update Details

  • Property: ibm.mq.container
  • Image: icr.io/ibm-messaging/mq
  • File: /home/runner/work/camel/camel/test-infra/camel-test-infra-ibmmq/src/main/resources/org/apache/camel/test/infra/ibmmq/services/container.properties
  • Old version: 10.0.0.0-r3
  • New version: 10.0.0.0-r4

Verification

Please verify:

  • Container image version is compatible with existing tests
  • No breaking changes in the updated version
  • Tests pass with the new version

Run the following to rebuild the test infra:

mvn clean verify -pl camel-test-infra-ibmmq

Then test the impacted components.


This PR was automatically created by the Container Version Upgrade workflow.

Update ibm.mq.container from 10.0.0.0-r3 to 10.0.0.0-r4
@github-actions github-actions Bot added dependencies Pull requests that update a dependency file container-images For check container upgrades automated For Check Container upgrade labels Aug 31, 2026
@gnodet

gnodet commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

✅ 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.
Failure verification
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
Full test output
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

Local integration tests run by ForgeBot on behalf of @gnodet
Tests run without -Dci.env.name to include ITs disabled on GitHub Actions CI

@apupier

apupier commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

wondering when these tests were broken, it was recently supposed to be working with IBM MQ 10 #25232

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated For Check Container upgrade container-images For check container upgrades dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants