[
https://issues.apache.org/jira/browse/MAHOUT-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399263#comment-13399263
]
Sebastian Schelter commented on MAHOUT-917:
-------------------------------------------
I'm not sure this is really an issue. You can always run particular tests from
the IDE or on the commandline via mvn. To simply build or check for compilation
errors, one can build using -DskipTests.
Waiting until the tests finish before you commit or upload a patch is not a big
hurdle in my eyes. I see it as a good thing that we have a huge number of
intensive tests.
> Build takes too long
> --------------------
>
> Key: MAHOUT-917
> URL: https://issues.apache.org/jira/browse/MAHOUT-917
> Project: Mahout
> Issue Type: Improvement
> Components: build
> Reporter: Frank Scholten
> Assignee: Sebastian Schelter
>
> On my machine a full mvn clean install takes 55 minutes.
> As an experiment I put all MapReduce job tests for all clustering algorithms
> on ignore. This reduces the build to 45 minutes. There are a lot of these
> long running tests in the project.
> What about creating a separate maven profile for the nightly build that run
> all MapReduce job tests? For this we have to move these MapReduce tests
> to separate classes with a naming convention such as *JobTest or
> *IntegrationTest and add some maven configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
