[
https://issues.apache.org/jira/browse/METRON-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063141#comment-16063141
]
ASF GitHub Bot commented on METRON-1004:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/624
I moved work from a mostly unrelated branch over here. Specifically, it
attempts to get the InMemoryComponents to be reused across a given test class.
This is particularly helpful for ProfilerIntegrationTest and
MaasIntegrationTest. It's not extended to everything (in particular single
test only classes). It does make the build run faster, but not necessarily
fast enough to solve this problem. There's also some cleanup that needs to be
taken care of.
Skadoo appears to be mostly resolved on this branch for some reason. It
also performs an actual thread.stop(), because it needs to actually kill.
> 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)
