[
https://issues.apache.org/jira/browse/KAFKA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424373#comment-13424373
]
Joe Stein commented on KAFKA-134:
---------------------------------
<< The reason that all the tests fail in Joe Stein's comment above is that
ScalaTest has not been updated. Updating it to scalatest_2.9.2 v1.8 will fix
this.
ok, the tests are running now (great) but 75 tests are failing ( :( )
looks like some issues
[info] - testBasic(kafka.javaapi.consumer.ZookeeperConsumerConnectorTest) ***
FAILED ***
[info] java.net.BindException: Address already in use
[info] at sun.nio.ch.Net.bind(Native Method)
[info] at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126)
[info] at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
[info] at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52)
[info] at
org.apache.zookeeper.server.NIOServerCnxn$Factory.<init>(NIOServerCnxn.java:144)
[info] at
org.apache.zookeeper.server.NIOServerCnxn$Factory.<init>(NIOServerCnxn.java:125)
[info] at kafka.zk.EmbeddedZookeeper.<init>(EmbeddedZookeeper.scala:31)
[info] at
kafka.zk.ZooKeeperTestHarness$class.setUp(ZooKeeperTestHarness.scala:30)
[info] at
kafka.javaapi.consumer.ZookeeperConsumerConnectorTest.setUp(ZookeeperConsumerConnectorTest.scala:34)
[info] at junit.framework.TestCase.runBare(TestCase.java:128)
[info] ...
and
[info] - testCollateAndSerializeEvents *** FAILED ***
[info] java.lang.AssertionError: Expectation failure on verify:
[info] multiSend([ProducerRequest(test1$topic,1,75),
ProducerRequest(test-topic,0,70), ProducerRequest(test-topic,1,70),
ProducerRequest(test1$topic,0,75)]): expected: 1, actual: 0
[info] at org.easymock.internal.MocksControl.verify(MocksControl.java:184)
[info] at org.easymock.EasyMock.verify(EasyMock.java:2038)
[info] at
kafka.producer.AsyncProducerTest.testCollateAndSerializeEvents(AsyncProducerTest.scala:292)
[info] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[info] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[info] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[info] at java.lang.reflect.Method.invoke(Method.java:597)
[info] at
org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
[info] at
org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
[info] at
org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
[info] ...
are the two biggest culprits, guessing something with the scalatest updates
from where we were to what is current.
trunk on my same machine runs fine (so the address in use is not localized it
is something in how the tests are running causing it)
I tried the scala2.9.2 branch of Chris's github fork but got the same issue I
had before (tests not even running)
> Upgrade Kafka to sbt 0.11.3
> ---------------------------
>
> Key: KAFKA-134
> URL: https://issues.apache.org/jira/browse/KAFKA-134
> Project: Kafka
> Issue Type: Improvement
> Components: packaging
> Reporter: Joshua Hartman
> Attachments: kafka-134-v2-draft.patch, kafka-134-v3-draft.patch,
> kafka_patch.txt
>
>
> Upgrading to sbt 0.10.1 is a nice to have as sbt moves forward. Plus, it's a
> requirement for me to help publish Kafka to maven :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
