[
https://issues.apache.org/jira/browse/METRON-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069050#comment-16069050
]
ASF GitHub Bot commented on METRON-1004:
----------------------------------------
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124922443
--- Diff:
metron-interface/metron-rest/src/test/java/org/apache/metron/rest/controller/KafkaControllerIntegrationTest.java
---
@@ -148,6 +150,15 @@ public void stop() {
@Before
public void setup() throws Exception {
+ runner = new ComponentRunner.Builder()
+ .withComponent("kafka", kafkaWithZKComponent)
+ .withCustomShutdownOrder(new String[]{"kafka"})
+ .build();
+ try {
+ runner.start();
+ } catch (UnableToStartException e) {
+ e.printStackTrace();
--- End diff --
I'd be ok with that. This will just mask an error until it fails later
less explicably.
> 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)
