Please sign in to comment.
Hardened junit long test RebalanceLongTest.java. Other test hardening.
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...
- Loading branch information...
Showing with 32 additions and 15 deletions.