[jira] [Commented] (STORM-1170) Consistent Unit Test failure in Travis in backtype.storm.utils.DisruptorQueueTest

["Zhuo Liu (JIRA)" <ji...@apache.org>]

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

Zhuo Liu commented on STORM-1170:
---------------------------------

I also met the same problem in CI. I think that is because the producer sometimes cannot finish publishing 1M tuples before TIMEOUT(100ms). The root cause is that the producer.interrupt() can set the interrupted flag to be true but not really terminate the producer thread (there is no blocking functions (sleep, wait, join) inside producer's run function, so no InterruptedException will be thrown).

We can solve the issue by checking the interrupted flag inside producer's run function. 

> Consistent Unit Test failure in Travis in backtype.storm.utils.DisruptorQueueTest
> ---------------------------------------------------------------------------------
>
>                 Key: STORM-1170
>                 URL: https://issues.apache.org/jira/browse/STORM-1170
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Boyang Jerry Peng
>            Priority: Minor
>
> testInOrder(backtype.storm.utils.DisruptorQueueTest)  Time elapsed: 2.141 sec  <<< FAILURE!
> junit.framework.AssertionFailedError: producer 0 is still alive
> 	at junit.framework.Assert.fail(Assert.java:57)
> 	at junit.framework.Assert.assertTrue(Assert.java:22)
> 	at junit.framework.Assert.assertFalse(Assert.java:39)
> 	at junit.framework.TestCase.assertFalse(TestCase.java:210)
> 	at backtype.storm.utils.DisruptorQueueTest.run(DisruptorQueueTest.java:112)
> 	at backtype.storm.utils.DisruptorQueueTest.testInOrder(DisruptorQueueTest.java:83)



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