Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flakey test: ITActiveMQSender #3633

Closed
codefromthecrypt opened this issue Dec 13, 2023 · 0 comments · Fixed by #3640
Closed

flakey test: ITActiveMQSender #3633

codefromthecrypt opened this issue Dec 13, 2023 · 0 comments · Fixed by #3640
Labels

Comments

@codefromthecrypt
Copy link
Member

ITActiveMQSender loops trying to connect to the VM transport in CI sometimes.

Here's an example from the JDK11 job

2023-12-13 04:59:18:131 [ActiveMQ Task-2] WARN org.apache.activemq.transport.failover.FailoverTransport - Failed to connect to [vm://embedded-broker?create=false] after: 30 attempt(s) with Broker named 'embedded-broker' does not exist., continuing to retry.

We should probably switch to a docker test image approach as we already have problems with this test library as it is pinned to junit4.

codefromthecrypt pushed a commit that referenced this issue Dec 13, 2023
Notably, this removes a JUnit 4 dependency in activemq and should fix
flakes related to ActiveMQ integration tests.

Fixes #3633

Signed-off-by: Adrian Cole <adrian@tetrate.io>
codefromthecrypt pushed a commit that referenced this issue Dec 13, 2023
Notably, this removes a JUnit 4 dependency in activemq and should fix
flakes related to ActiveMQ integration tests.

Fixes #3633

Signed-off-by: Adrian Cole <adrian@tetrate.io>
codefromthecrypt added a commit that referenced this issue Dec 13, 2023
Notably, this removes a JUnit 4 dependency in activemq and should fix
flakes related to ActiveMQ integration tests.

Fixes #3633

Signed-off-by: Adrian Cole <adrian@tetrate.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant