You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Chuck Burgess (JIRA)" <ji...@apache.org> on 2015/11/06 17:58:28 UTC
[jira] [Assigned] (STORM-1183) Intermittent testInOrder failures
seen in Travis builds
[ https://issues.apache.org/jira/browse/STORM-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chuck Burgess reassigned STORM-1183:
------------------------------------
Assignee: Chuck Burgess
> 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
> Assignee: 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)