[ 
https://issues.apache.org/jira/browse/METRON-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858089#comment-15858089
 ] 

ASF GitHub Bot commented on METRON-705:
---------------------------------------

Github user cestella commented on the issue:

    https://github.com/apache/incubator-metron/pull/444
  
    I reran this 7 times on my travis account for the most recent commit and 
the times were on average 32 minutes 53 seconds
    
    * 28m 17s
    * 28m 13s
    * 46m 28s
    * 35m 53s
    * 26m 26s
    * 33m 0s
    * 31m 57s
    
    
![build_times](https://cloud.githubusercontent.com/assets/540359/22742453/cbf11ea0-ede4-11e6-8f9c-d1a6af5196bc.png)



> Parallelize the build in travis to the extent that is obvious
> -------------------------------------------------------------
>
>                 Key: METRON-705
>                 URL: https://issues.apache.org/jira/browse/METRON-705
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Casey Stella
>            Assignee: Casey Stella
>
> Travis suggests at 
> https://blog.travis-ci.com/2012-11-28-speeding-up-your-tests-by-parallelizing-them/
>  that for situations where the integration get chunky, we can parallelize 
> them using their build matrix.  Also, if we can separate those out, we can 
> also process-parallelize the unit and build.
> This is just a stopgap that requires no code changes to lower build 
> wall-clock times.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to