[
https://issues.apache.org/jira/browse/MAHOUT-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113985#comment-14113985
]
Hudson commented on MAHOUT-1610:
--------------------------------
SUCCESS: Integrated in Mahout-Quality #2766 (See
[https://builds.apache.org/job/Mahout-Quality/2766/])
MAHOUT-1610 Update tests to pass in Java 8; closes apache/mahout#46 (srowen:
rev 91f15ecfe5d26de36d8e9bcd6cf109b307882a32)
*
mrlegacy/src/test/java/org/apache/mahout/classifier/df/tools/VisualizerTest.java
* math/src/test/java/org/apache/mahout/math/random/MultinomialTest.java
* mrlegacy/src/test/java/org/apache/mahout/clustering/TestClusterInterface.java
* mrlegacy/src/test/java/org/apache/mahout/common/StringUtilsTest.java
* mrlegacy/src/main/java/org/apache/mahout/clustering/ClusteringUtils.java
* integration/src/test/resources/expected-arff-schema-2.json
* integration/src/test/resources/expected-arff-dictionary-2.csv
* mrlegacy/src/test/java/org/apache/mahout/classifier/df/DecisionForestTest.java
* mrlegacy/src/test/java/org/apache/mahout/classifier/df/data/DatasetTest.java
* integration/src/test/java/org/apache/mahout/utils/vectors/arff/DriverTest.java
> Tests can be made more robust to pass in Java 8
> -----------------------------------------------
>
> Key: MAHOUT-1610
> URL: https://issues.apache.org/jira/browse/MAHOUT-1610
> Project: Mahout
> Issue Type: Bug
> Components: Integration
> Affects Versions: 0.9
> Environment: Java 1.8.0_11 OS X 10.9.4
> Reporter: Sean Owen
> Assignee: Sean Owen
> Priority: Minor
> Labels: java8, tests
> Fix For: 1.0
>
>
> Right now, several tests don't seem to pass when run with Java 8 (at least on
> Java 8). The failures are benign, and just due to tests looking for
> too-specific values or expecting things like a certain ordering of hashmaps.
> The tests can easily be made to pass both Java 8 and Java 6/7 at the same
> time by either relaxing the tests in a principled way, or accepting either
> output of two equally valid ones as correct.
> (There's also one curious compilation failure in Java 8, related to generics.
> It is fixable by changing to a more explicit declaration that should be
> equivalent. It should be entirely equivalent at compile time, and of course,
> at run time. I am not sure it's not just a javac bug, but, might as well work
> around when it's so easy.)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
