Voldemort junit tests (how to run + failures)

[Vanessa Williams]

Hi all, because I'm about to make some fairly major changes to Voldemort for our usage (ripping out bdb), I wanted to make sure all junit tests passed on the unadulterated version first.

The first problem I had was that I could not get 'ant junit' to run the tests successfully. The resulting report complains mightily about many classes not having no-arg constructors. As far as I could determine this was because test classes both extended TestCase AND used JUnit 4 annotations, such as @RunWith(Parameterized.class). Supposedly, it's either one or the other, not both.

So, my first question is: 

- does anyone know how to successfully run the ant target "junit" without modifying a whack of test classes? Is there a magic incantation that will make them run properly as is?

In the meantime, I spent quite some time "repairing" the test classes that ant/junit didn't like and was able to run the tests and get some more meaningful output. However, there was one significant failure.

My second question is:

- has anyone else seen the RebalanceTest fail, like so:

testRWRebalanceFourNodes[3]

Failure

Rebalance failed on rebalance task id 59 junit.framework.AssertionFailedError: Rebalance failed on rebalance task id 59 at voldemort.client.rebalance.AbstractRebalanceTest.testRWRebalanceFourNodes(AbstractRebalanceTest.java:731) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680)

Is this a known problem?

Thanks in advance for any insight. Once I can get these tests to run cleanly, I can try them against my butchered version for comparison.

Regards,

Vanessa

ThoughtWire Corp.

www.thoughtwire.ca

[Vin C]

ant junit-long should run evrything.. This is an intermittent failure we have seen in rebalance..

All of rebalancing code and tests is going to change drastically from next release. So, feel free to move on, if this is the only failure you are seeing..