jamesnetherton commented on issue #5081: URL: https://github.com/apache/camel-quarkus/issues/5081#issuecomment-1825487888
Turns out this is partially related to test ordering. The problem is that `HazelcastInstanceTest` adds a new member instance to the cluster, but it does not wait or verify that it was shut down after the test completes. In fact, it currently does not shut down the [correct member](https://github.com/apache/camel-quarkus/blob/main/integration-tests/hazelcast/src/test/java/org/apache/camel/quarkus/component/hazelcast/it/HazelcastTestResource.java#L42). Thus when the other tests run afterwards, the cluster can be temporarily in a state where operations can fail. -- 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]
