build.xml - bumped all maxmemory settings to 2048m - Placed a 90 minute timeout on the long test at ant level. test/long/voldemort/client/rebalance/RebalanceLongTest.java - null out some objects in the hopes of reducing the overall memory footprint of these tests. We are truly abusing junit with a long-running, multi-threaded test, that has 10 sub tests and 4 distinct parameter settings. test/unit/voldemort/client/rebalance/AbstractRebalanceTest.java - start of tests is not clear in junit log output. Added logger.info to start of tests to make grepping through the log when tests have failed badly and/or are running in an infitie loop easier. - Bumped each test timeout up to 10 minutes. Again, note abuse of junit: tests should not be defined at the abstract class level. This makes it hard to set appropriate limits (such as timeout) for each specific test. Long tests should have a different timeout than short tests...
is necessary for me to debug these tests and easily run all the other tests. (By 'hang', I mean get into a state where clients run forever complaining that there are not enough servers.) Wrapping with timeouts is done both at the Junit level (i.e., "@Test(timeout = ...") and at the ant level (i.e., for an entire unit test). Switched the tests I was touching to use Junit4 idiom rather than Junit3 idiom. I.e., removed the 'extends TestCase' from the class declaration. Upped the memory allowed for all junit tets in ant from 1024m to 2048m since I ran into ant out of memory errors.
junit ant targets. The report is useful because for a test class with many sub-tests, the report clearly explains which sub-tests failed. Unlike other ant junit targets, this target also produce a plain text report. The plain text report is useful for running a single test in a loop until it fails. Clarified the help message for the 'junit-test' ant target.
The large tests are copied to the test/large To run short tests for sanity check purpose: ant junit To run short and long tests: ant junit-long To run short, long and contrib tests: ant junit-all
…dual unit tests as follows - ant junit-test -Dtest.name=<class_name>
…using the Cobertura" Reverting it since it pollutes the junit output This reverts commit c6a9034.
…e Cobertura library (http://cobertura.sourceforge.net/). A nice introductory article can be found at http://www.ibm.com/developerworks/java/library/j-cobertura/ The results are reported both in HTML format for humans, and in an XML format suitable for other tools, such as the Cobertura plugin for the Hudson continuous integration server. To view the report, run "ant coverage" and then view the dist/coverage/html/index.html file in your browser.
…e their own targets
…all, best to supress deprecation warnings.
…rget to build.xml
…Ant task. Also allowing overrides of the properties from the EC2 properties file via system properties
…ttp://forums.sun.com/thread.jspa?threadID=5136911), allowing suppressing of error messages on cluster shut down, and renaming SmokeTest to Ec2SmokeTest (for pattern matching in the unit test Ant task).
ant conditions just check if the property isset or not. there is no easy way to unset a property in general added an additional check for empty strings in $BUILD_NUMBER to set the snapshot name for ant snapshot target.