[GitHub] [camel-quarkus] ppalaga commented on issue #5081: HazelcastMapTest fails when run after HazelcastIdempotentTest and HazelcastInstanceTest
ppalaga commented on issue #5081: URL: https://github.com/apache/camel-quarkus/issues/5081#issuecomment-1625690560 It looks like the HazelcastInstanceTest calling HazelcastTestResource.addMemberToCluster() makes the HazelcastMapTest fail, but only if some other test (e.g. HazelcastIdempotentTest) was run before HazelcastInstanceTest. I am not sure the fix in https://github.com/apache/camel-quarkus/pull/5082/files is actually not sweeping the real issue under the carpet. I guess the subsequent tests should work regardless of how many nodes the cluster has? And I guess all these tests were passing in the past? -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #5081: HazelcastMapTest fails when run after HazelcastIdempotentTest and HazelcastInstanceTest
ppalaga commented on issue #5081: URL: https://github.com/apache/camel-quarkus/issues/5081#issuecomment-1680918369 > @ppalaga is there any update? Not really. I do not feel to be a Hazelcast and camel-hazelcast expert to tell whether cluster topology changes happening after a Camel app was started are expected to impact the events received by the app. Here apparently, if a node is added, the app does not receive some events after that. Is that expected @davsclaus? -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org