[
https://issues.apache.org/jira/browse/STORM-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992590#comment-14992590
]
ASF GitHub Bot commented on STORM-1183:
---------------------------------------
GitHub user ashnazg opened a pull request:
https://github.com/apache/storm/pull/864
STORM-1183: bump timeout to 10s, since test case isn't really testing speed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashnazg/storm falseNegatives
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/864.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #864
----
commit cfc960da6451570fc6825bfa38455c7e667ffa88
Author: Chuck Burgess <[email protected]>
Date: 2015-11-05T22:07:52Z
bump timeout to 10s, since test case isn't really testing speed
----
> Intermittent testInOrder failures seen in Travis builds
> -------------------------------------------------------
>
> Key: STORM-1183
> URL: https://issues.apache.org/jira/browse/STORM-1183
> Project: Apache Storm
> Issue Type: Test
> Affects Versions: 0.10.0
> Reporter: Chuck Burgess
> Priority: Minor
>
> DisruptorQueueTests::testInOrder has some assertions that pay attention to
> whether or not producer instances shut down quickly.
> (https://travis-ci.org/apache/storm/jobs/89506537)
> Since the test case itself focuses the ordering of processing rather than
> speed, I'd suggest bumping TIMEOUT up from the current 1s to 10s... maybe
> consistent failures with such a large timeout would be more useful as visible
> test failures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
