lanking520 commented on a change in pull request #13046: [MXNET-1155] Add scala 
packageTest utility
URL: https://github.com/apache/incubator-mxnet/pull/13046#discussion_r240026393
 
 

 ##########
 File path: scala-package/packageTest/README.md
 ##########
 @@ -0,0 +1,68 @@
+# MXNet Scala Package Test
+
+This is an project created to run the test suite on a fully packaged mxnet 
jar. The test suite is found locally but mxnet is from the target jarfile.
+
+## General Setup
+
+To setup the packageTest, you must first build your tests. To build the tests, 
follow these steps from the mxnet main directory:
+
+1. Build MXNet and the scala package from source following the directions 
[here](https://mxnet.incubator.apache.org/install/scala_setup.html#source)
+2. Build the tests by running `make scalatestcompile`.
+3. Follow setup instructions below for your testing goal
+
+## Running
+
+There are three different modes of operation for testing based on the location 
of the jar and where it is coming from:
+
+### Test Installed Jars
+
+If you have a jar file, you can install it to your maven cache 
repository(`~/.m2/repository`) using `mvn install:install-file 
-Dfile=<path-to-file>`.  This might be useful if you acquire the .jar file from 
elsewhere. You can also run `make scalainstall` to install from a local build. 
Then, run `make testinstall` in the package test directory to run the tests.  
Note that unless you also install an additional mxnetexamples jar, you can only 
run the unit tests.
 
 Review comment:
   Currently as @frankfliu tested `mvn install:install-file 
-Dfile=<path-to-file>` seemed not functioning properly. Mac OSX crash and Linux 
Machine installed into a wrong jar. Please double check about this section

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to