[
https://issues.apache.org/jira/browse/STORM-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038188#comment-15038188
]
ASF GitHub Bot commented on STORM-1364:
---------------------------------------
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/916#issuecomment-161728319
```
testPollWhileThereAreNoDataAvailable(backtype.storm.utils.ShellBoltMessageQueueTest)
Time elapsed: 1.005 sec <<< FAILURE!
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at
backtype.storm.utils.ShellBoltMessageQueueTest.testPollWhileThereAreNoDataAvailable(ShellBoltMessageQueueTest.java:55)
```
This is the test I see failing both in this pull request and also on my
travis
ci setup.
It does not seem related to my changes, but it is causing the overall check
to
fail for storm-core, and that causes the other modules not to be tested.
> Log storm version on daemon start
> ---------------------------------
>
> Key: STORM-1364
> URL: https://issues.apache.org/jira/browse/STORM-1364
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
> Reporter: Derek Dagit
> Assignee: Derek Dagit
> Priority: Minor
>
> As an admin, I would like each storm daemon to log its version of storm, so
> that I can more easily root cause issues happening near an upgrade of the
> cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
