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

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_r124821164
  
    --- Diff: 
metron-platform/metron-parsers/src/test/java/org/apache/metron/parsers/integration/ParserDriver.java
 ---
    @@ -0,0 +1,168 @@
    +/**
    --- End diff --
    
    As I see it, there are a couple of things we want to test for every parser:
    * The parser works (i.e. the unit tests we currently have)
    * The parser can be driven from within the `ParserBolt` (the current 
integration tests as of this PR)
    
    Beyond that, I think it's reasonable to have a `ParserIntegrationTest` 
which just validates data flows through the parser topology assuming a 
correctly working parser and just validates that things work within Storm.  I 
would not expect every parser to require this kind of test.  We have something 
similar to that in `SimpleHbaseEnrichmentWriterIntegrationTest`.


> 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)

Reply via email to