[
https://issues.apache.org/jira/browse/STORM-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997528#comment-14997528
]
ASF GitHub Bot commented on STORM-1191:
---------------------------------------
Github user ashnazg commented on the pull request:
https://github.com/apache/storm/pull/869#issuecomment-155220143
True, but if the original issue is just that Travis is slow, ;-) ... I just
want to minimize the false negatives of test failures that are caused when
Travis is bogged down and the test case runs too slow. I presume that the test
will _logically_ pass if given enough time, and that the test case itself is
not trying to enforce a performance speed spec.
> Random test failures on backtype.storm.transactional-test
> ---------------------------------------------------------
>
> Key: STORM-1191
> URL: https://issues.apache.org/jira/browse/STORM-1191
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Chuck Burgess
> Assignee: Chuck Burgess
> Priority: Minor
>
> Travis builds show occasional backtype.storm.transactional-test failures due
> to the 100s timeout (https://travis-ci.org/apache/storm/jobs/90105000).
> Assuming this is not a performance test, I'll submit PR to bump timeout by
> 50% to cut back on these failures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
