You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/26 19:32:45 UTC

[jira] [Commented] (KAFKA-4744) Streams_bounce test failing occassionally

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

ASF GitHub Bot commented on KAFKA-4744:
---------------------------------------

GitHub user enothereska opened a pull request:

    https://github.com/apache/kafka/pull/2601

    KAFKA-4744: Increased timeout for bounce test

    

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

    $ git pull https://github.com/enothereska/kafka KAFKA-4744-bounce

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

    https://github.com/apache/kafka/pull/2601.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 #2601
    
----
commit 3acabbf7be4230c222e33ff9e3bc0c1de9329287
Author: Eno Thereska <en...@gmail.com>
Date:   2017-02-26T19:31:46Z

    Increased timeout

----


> Streams_bounce test failing occassionally
> -----------------------------------------
>
>                 Key: KAFKA-4744
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4744
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.2.0
>            Reporter: Eno Thereska
>             Fix For: 0.10.3.0
>
>
> The test occasionally fails, e.g., in https://jenkins.confluent.io/job/system-test-kafka/499/console.
> The message is:
> kafkatest.tests.streams.streams_bounce_test.StreamsBounceTest.test_bounce: FAIL: Streams Test process on ubuntu@worker5 took too long to exit
> Traceback (most recent call last):
>   File "/var/lib/jenkins/workspace/system-test-kafka/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.6.0-py2.7.egg/ducktape/tests/runner_client.py", line 123, in run
>     data = self.run_test()
>   File "/var/lib/jenkins/workspace/system-test-kafka/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.6.0-py2.7.egg/ducktape/tests/runner_client.py", line 176, in run_test
>     return self.test_context.function(self.test)
>   File "/var/lib/jenkins/workspace/system-test-kafka/kafka/tests/kafkatest/tests/streams/streams_bounce_test.py", line 72, in test_bounce
>     self.processor1.stop()
>   File "/var/lib/jenkins/workspace/system-test-kafka/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.6.0-py2.7.egg/ducktape/services/service.py", line 255, in stop
>     self.stop_node(node)
>   File "/var/lib/jenkins/workspace/system-test-kafka/kafka/tests/kafkatest/services/streams.py", line 77, in stop_node
>     wait_until(lambda: not node.account.alive(pid), timeout_sec=60, err_msg="Streams Test process on " + str(node.account) + " took too long to exit")
>   File "/var/lib/jenkins/workspace/system-test-kafka/kafka/venv/local/lib/python2.7/site-packages/ducktape-0.6.0-py2.7.egg/ducktape/utils/util.py", line 36, in wait_until
>     raise TimeoutError(err_msg)
> TimeoutError: Streams Test process on ubuntu@worker5 took too long to exit
> Looking at the logs it looks like the test succeeded, so it might be that we need to slightly increase the time we wait for.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)