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

ASF GitHub Bot commented on STORM-1844:
---------------------------------------

GitHub user srdo opened a pull request:

    https://github.com/apache/storm/pull/1421

    STORM-1844: Make netty unit test use STORM_TEST_TIMEOUT_MS, increase …

    …STORM_TEST_TIMEOUT_MS to 10 seconds, increase DisruptorQueueTest timeout 
to 5 seconds from 1
    
    Link for convenience https://issues.apache.org/jira/browse/STORM-1844

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/srdo/storm STORM-1844

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/1421.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 #1421
    
----
commit 653465a163f382cdcfd1672a97b5280abc1465c2
Author: Stig Rohde Døssing <[email protected]>
Date:   2016-05-17T09:31:08Z

    STORM-1844: Make netty unit test use STORM_TEST_TIMEOUT_MS, increase 
STORM_TEST_TIMEOUT_MS to 10 seconds, increase DisruptorQueueTest timeout to 5 
seconds from 1

----


> Some tests are flaky due to low timeout
> ---------------------------------------
>
>                 Key: STORM-1844
>                 URL: https://issues.apache.org/jira/browse/STORM-1844
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 2.0.0
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Minor
>
> We saw a few test failures likely due to low timeouts 
> https://github.com/apache/storm/pull/1417#issuecomment-219545865. The 
> timeouts for these tests should be increased, and the test mentioned by 
> [~kishorvpatil] should reflect STORM_TEST_TIMEOUT_MS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to