[
https://issues.apache.org/jira/browse/SYSTEMML-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321010#comment-15321010
]
Deron Eriksson commented on SYSTEMML-478:
-----------------------------------------
Tried removing maven-surefire-plugin version and maven-failsafe-plugin version
so that they would use the Apache parent pom version (2.19.1).
Running test suite on OS X (with version 2.19.1), I saw the following:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify (default) on
project systemml: There was a timeout or other error in the fork
{code}
In addition, some of the output referred to numbers rather than test case
names. I saw things like this:
{code}
Running [2]
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 82.2 sec - in
[2]
{code}
rather than all of the 'running' output looking similar to this:
{code}
Running org.apache.sysml.test.integration.functions.jmlc.FrameCastingTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.694 sec - in
org.apache.sysml.test.integration.functions.jmlc.FrameCastingTest
{code}
So I would say we should probably stick with 2.17 for now.
> Upgrade maven-failsafe-plugin if fixed
> --------------------------------------
>
> Key: SYSTEMML-478
> URL: https://issues.apache.org/jira/browse/SYSTEMML-478
> Project: SystemML
> Issue Type: Improvement
> Reporter: Deron Eriksson
> Priority: Minor
>
> The maven-failsafe-plugin entry in pom.xml is set to version 2.17 due to:
> "Failsafe 2.18 has a bug in computing # cores, so use 2.17"
> The maven central repo has the following later versions of
> maven-failsafe-plugin available:
> 2.19.1
> 2.19
> 2.18.1
> We should determine if a later version of the plugin can be used and the
> "HACK ALERT" message can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
