You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:36:14 UTC

[jira] (MERCURY-40) DefaultSatSolver is non-deterministic

     [ https://jira.codehaus.org/browse/MERCURY-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MERCURY-40.
---------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

Assignee, if you think you can fix this bug anytime soon, please reopen and proceed appropriately.

> DefaultSatSolver is non-deterministic
> -------------------------------------
>
>                 Key: MERCURY-40
>                 URL: https://jira.codehaus.org/browse/MERCURY-40
>             Project: Mercury (retired)
>          Issue Type: Bug
>    Affects Versions: 1.0.0-alpha-2
>            Reporter: Benjamin Bentmann
>            Assignee: Oleg Gusakov
>         Attachments: mercury-failed.txt, mercury-passed.txt, org.apache.maven.mercury.metadata.sat.DefaultSatSolverTest.txt
>
>
> Running the unit test {{DefaultSatSolverTest.testSingleVersionResolution()}} once on Java 1.5 and 1.6 revealed a bug in {{DefaultSatSolver.solve()}} due to usage of {{HashMap}}. See attached logs (passed with 1.5, failed with 1.6).
> The internal tweaks to the hash algos employed by the different JRE versions exhibited a non-deterministic ordering of the artifact metadata list.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)