Determine why IT is failing when using Pulsar 4.0.2
#1014
Labels
theme: testing
Issues related to testing
Comments
onobc
added a commit
that referenced
this issue
Jan 21, 2025
This sets the image tag from `latest` to `3.3.4` in order to ensure the default tag matches up w/ the version of Pulsar supported by Spring for Apache Pulsar. See #1014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
The DefaultTenantAndNamespaceTests reactive IT is failing when running against Pulsar server
4.0.2.Determine why and re-enable once accounted for.
Details
This IT sets the default tenant and namespace for Spring Pulsar to use and sends 10 message and expects to consume 10 messages:
If the Pulsar container image is < 4.0.2 everything is fine.
However, when set to 4.0.2 it fails to consume some of the messages (reactive client only).
Failed run: https://github.com/spring-projects/spring-pulsar/actions/runs/12892190231/job/35945871536#step:5:973
The text was updated successfully, but these errors were encountered: