Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/486#issuecomment-95734278
https://travis-ci.org/HeartSaVioR/storm/builds/59794019 succeed and
https://travis-ci.org/HeartSaVioR/storm/builds/59795636 failed, which means
failed tests could be a kind of random failures or relied on machine power.
First one is DisruptorQueueTest, as you already know.
Failed tests:
testMessageDisorder(backtype.storm.utils.DisruptorQueueTest): We expect to
receive first published message first, but received null expected:<1> but
was:<null>
Second one is Kafka Tests, which I met intermittently from my dev. machine.
testKeyValue(storm.kafka.TridentKafkaTest): Could not send message with
key = key-123 to topic = test
generateTuplesWithKeyAndKeyValueScheme(storm.kafka.KafkaUtilsTest): Error
fetching data from [Partition{host=localhost:52047, partition=0}] for topic
[testTopic]: [OFFSET_OUT_OF_RANGE]
---
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.
---
