You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamás Cservenák (Jira)" <ji...@apache.org> on 2022/02/25 09:55:00 UTC

[jira] [Updated] (MRESOLVER-245) Isolate Hazelcast tests

     [ https://issues.apache.org/jira/browse/MRESOLVER-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamás Cservenák updated MRESOLVER-245:
--------------------------------------
    Fix Version/s: 1.8.0

> 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
>            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)