I have invoked mvn test with the -DwildcardSuites option to specify a single BinarizerSuite scalatest suite.
The command line is mvn -pl mllib -Pyarn -Phadoop-2.6 -Dhadoop2.7.1 -Dscala-2.11 -Dmaven.javadoc.skip=true -DwildcardSuites=org.apache.spark.ml.feature.BinarizerSuite test The scala side of affairs is correct: here is the relevant output Results : Discovery starting. Discovery completed in 2 seconds, 614 milliseconds. Run starting. Expected test count is: 3 BinarizerSuite: - params - Binarize continuous features with default parameter - Binarize continuous features with setter Run completed in 6 seconds, 311 milliseconds. Total number of tests run: 3 So we see only the one scala test suite was run- as intended. But on the java side it seems all of the tests within the mllib project were run. Here is a snippet: Running org.apache.spark.ml.attribute.JavaAttributeGroupSuite Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.156 sec - in org.apache.spark.ml.attribute.JavaAttributeGroupSuite Running org.apache.spark.ml.attribute.JavaAttributeSuite Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.018 sec - in org.apache.spark.ml.attribute.JavaAttributeSuite Running org.apache.spark.ml.classification.JavaDecisionTreeClassifierSuite Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.79 sec - in .. dozens of similar .. Running org.apache.spark.mllib.tree.JavaDecisionTreeSuite Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.287 sec - in org.apache.spark.mllib.tree.JavaDecisionTreeSuite -- org.jblas INFO Deleting /sparks/sparkup/mllib/target/tmp/jblas6038907640270970048/libjblas.dylib -- org.jblas INFO Deleting /sparks/sparkup/mllib/target/tmp/jblas6038907640270970048/libjblas_arch_flavor.dylib -- org.jblas INFO Deleting /sparks/sparkup/mllib/target/tmp/jblas6038907640270970048 Results : Tests run: 106, Failures: 0, Errors: 0, Skipped: 0 So what is the mvn option / setting to disable the java tests? ...
