Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1417#issuecomment-219600127
@kishorvpatil
Nice finding. I think it should reflect STORM_TEST_TIMEOUT_MS, but it can
be done with another JIRA issue since it seems not related on this PR.
Btw, other test failure is observed from Travis CI, which I think is also
not related to this PR.
```
Running org.apache.storm.utils.DisruptorQueueTest
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.352 sec
<<< FAILURE! - in org.apache.storm.utils.DisruptorQueueTest
testInOrderBatch(org.apache.storm.utils.DisruptorQueueTest) Time elapsed:
0.405 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
org.apache.storm.utils.DisruptorQueueTest.run(DisruptorQueueTest.java:135)
at
org.apache.storm.utils.DisruptorQueueTest.testInOrderBatch(DisruptorQueueTest.java:106)
```
@srdo
I guess what @kishorvpatil reported is a kind of intermittent failure,
since one of storm-core build is passed on Travis CI.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
