[
https://issues.apache.org/jira/browse/MAHOUT-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163857#comment-13163857
]
Isabel Drost commented on MAHOUT-917:
-------------------------------------
As much as I would like to see those long running tests optimised I think that
is not going to happen any time soon. So I am very much in favour of your
proposed solution.
One warning: I already hear complaints from those using an IDE to run the whole
test suite by right clicking the test folder that all tests are being executed.
Being one of those seemingly rare human beings who mostly interacts with maven
from the command line I do not care personally.
> 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
>
> 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
