I had a long running sbt process on my laptop, when I saw these OOME
exceptions. They just disappeared the next day, when I restarted the
process.
Seems like this is a known issue in SBT versions <= 0.7.7 -
https://groups.google.com/group/simple-build-tool/browse_thread/thread/884a2f51804a3d91
Up
Thanks! I kept seeing this failure sporadically on the build server,
but have been unable to reporoduce it locally. It might be yet another
timing problem :-( Ticket created:
https://issues.apache.org/jira/browse/KAFKA-146
I think this is unrelated to the other unit tests errors reported on the
Hi,
I get the following errors when running sbt release-zip:
[info] Test Starting: testUnreachableServer
First message send retries took 10038 ms
[error] Test Failed: testUnreachableServer
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework
I have not seen that failure, but I get LogManagerTest failures often
locally. There is a nearby TODO about sleeps and time for metadata updates.
info] == core-kafka / kafka.log.LogManagerTest ==
[info] Test Starting: testCreateLog
[info] Test Passed: testCreateLog
[info] Test Starting: testClean
I got some transient failures, but not because of OOME.
Jun
On Sun, Sep 25, 2011 at 4:25 PM, Neha Narkhede wrote:
> Hi,
>
> I see that one unit test (kafka.javaapi.integration.PrimitiveApiTest)
> is broken on trunk. It runs into an OOME [1].
> Is anyone else seeing this too ?
>
> Thanks,
> Neha
Hi,
I see that one unit test (kafka.javaapi.integration.PrimitiveApiTest)
is broken on trunk. It runs into an OOME [1].
Is anyone else seeing this too ?
Thanks,
Neha
1. [info] == kafka.javaapi.integration.PrimitiveApiTest ==
[info] Test Starting:
testProduceAndFetch(kafka.javaapi.integration.Pri
