[
https://issues.apache.org/jira/browse/METRON-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069835#comment-16069835
]
ASF GitHub Bot commented on METRON-1004:
----------------------------------------
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r125007493
--- Diff:
metron-interface/metron-rest/src/test/java/org/apache/metron/rest/controller/KafkaControllerIntegrationTest.java
---
@@ -61,6 +62,7 @@
private static final int KAFKA_RETRY = 10;
@Autowired
private KafkaComponent kafkaWithZKComponent;
+ private ComponentRunner runner;
--- End diff --
I'm going to add a comment specifically pointing to that ticket, and noting
that this test is an outlier in terms of how we actually test.
@cestella Is there anything else in particular that you'd like to see in
order to at least mitigate risk of propagating test issues like this until we
upgrade spring?
> 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)
