[
https://issues.apache.org/jira/browse/STORM-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058253#comment-15058253
]
ASF GitHub Bot commented on STORM-1377:
---------------------------------------
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/941#issuecomment-164813457
1 kafka test timed out:
```
Tests run: 18, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 30.722 sec
<<< FAILURE! - in storm.kafka.KafkaUtilsTest
getOffsetFromConfigAndFroceFromStart(storm.kafka.KafkaUtilsTest) Time
elapsed: 2.732 sec <<< FAILURE!
java.lang.AssertionError: org.apache.kafka.common.errors.TimeoutException:
Failed to update metadata after 1000 ms.
at org.junit.Assert.fail(Assert.java:88)
at
storm.kafka.KafkaUtilsTest.createTopicAndSendMessage(KafkaUtilsTest.java:246)
at
storm.kafka.KafkaUtilsTest.createTopicAndSendMessage(KafkaUtilsTest.java:228)
at
storm.kafka.KafkaUtilsTest.getOffsetFromConfigAndFroceFromStart(KafkaUtilsTest.java:132)
```
> nimbus_auth_test: very short timeouts causing spurious failures
> ---------------------------------------------------------------
>
> Key: STORM-1377
> URL: https://issues.apache.org/jira/browse/STORM-1377
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 0.10.0, 0.11.0
> Reporter: Derek Dagit
> Assignee: Derek Dagit
> Priority: Minor
>
> This is caused by a units mismatch. We are waiting 30 ms for the thrift
> server to reply when we thought we were waiting 30s. This means that
> sometimes when we expect NotAliveException, we instead get
> TTransportException(SocketTimeoutException), and this fails the assertions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
