[
https://issues.apache.org/jira/browse/METRON-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065024#comment-16065024
]
ASF GitHub Bot commented on METRON-1004:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/624
Most recent commit, as @ottobackwards points out, merits some explanation.
Specifically it turns off the jacoco:prepare-agent from the Travis build
and allows us to just run the tests directly without it. We don't actually
produce the reports here, so it's pretty extraneous.
Locally this resulted in:
```
mvn -q -T 2C surefire:test@unit-tests 309.46s user 20.20s system 169% cpu
3:14.92 total
mvn -q -T 2C jacoco:prepare-agent surefire:test@unit-tests 555.20s user
25.93s system 254% cpu 3:47.90 total
```
> Travis CI - Job Exceeded Maximum Time Limit
> -------------------------------------------
>
> Key: METRON-1004
> URL: https://issues.apache.org/jira/browse/METRON-1004
> Project: Metron
> Issue Type: Bug
> Reporter: Nick Allen
> Fix For: Next + 1
>
>
> Most Travis CI jobs are failing with the following error message.
> bq. The job exceeded the maximum time limit for jobs, and has been terminated.
> Travis apparently has a hard 50 minute limit that will cause jobs to timeout.
>
> https://docs.travis-ci.com/user/customizing-the-build#Build-Timeouts
> There is some additional time for setting up the container that is counted in
> this hard 50 minute limit that is not reported in the UI. So even if a build
> says it took 44 minutes with a timeout, it likely in fact did hit the 50
> minute limit.
> Here are some examples of these failures.
> * https://travis-ci.org/apache/metron/builds/244574987
> * https://travis-ci.org/apache/metron/builds/244552768
> * https://travis-ci.org/apache/metron/builds/241249480
> This is a separate issue from the "Storm slots didn't shut down" issue that
> is tracked in a separate PR.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
