[
https://issues.apache.org/jira/browse/MRESOLVER-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504789#comment-17504789
]
Hudson commented on MRESOLVER-245:
----------------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #11
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/11/
> Isolate Hazelcast tests
> -----------------------
>
> Key: MRESOLVER-245
> URL: https://issues.apache.org/jira/browse/MRESOLVER-245
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamás Cservenák
> Assignee: Tamás Cservenák
> Priority: Major
> Fix For: 1.8.0
>
>
> The named-locks-hazelcast module uses Hazelcast. The IT tests were not
> properly isolated, so Hazelcast instances are able to discover other
> Hazelcast instances running locally or on same network. This causes sporadic
> IT failures, usually on CI, where multiple permutations are being run
> possibly next to each other.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
