[
https://issues.apache.org/jira/browse/MAHOUT-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163866#comment-13163866
]
Sean Owen commented on MAHOUT-917:
----------------------------------
I don't know if it's so hard... a few tests have been checked in that take over
30 minutes to run (one in the last week!) that I 'fixed' relatively easily.
They were running on a test input that was perhaps 100x bigger than it needed
to be.
If you run, you'll see a handful of tests taking well over half that time. I
think it'd be awful nice if the authors went back and tried to just run a
smaller test. Or disable them.
In fact I'd be fine with: if it takes more than 3 minutes to run it should be
disabled until the contributor can fix it.
> 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
