You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mahout.apache.org by "Suneel Marthi (JIRA)" <ji...@apache.org> on 2013/07/25 14:37:49 UTC

[jira] [Updated] (MAHOUT-917) Build takes too long

     [ https://issues.apache.org/jira/browse/MAHOUT-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suneel Marthi updated MAHOUT-917:
---------------------------------

    Affects Version/s: 0.6
                       0.7
        Fix Version/s: 0.8
    
> Build takes too long
> --------------------
>
>                 Key: MAHOUT-917
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-917
>             Project: Mahout
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.6, 0.7
>            Reporter: Frank Scholten
>            Assignee: Sebastian Schelter
>             Fix For: 0.8
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira