Skip to content
This repository

Oct 17, 2012

  1. Jay Wylie

    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...
    jayjwylie authored

Oct 09, 2012

  1. Jay Wylie

    Wrapped tests that hang because of my changes with timeouts. This

    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.
    jayjwylie authored
  2. Jay Wylie

    Made ant target 'junit-test' produce a report like all the other

    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.
    jayjwylie authored

Sep 20, 2012

  1. Fixed the merge issues from master. Fixed a bug in SocketStoreClientF…

    …actoryMbeanTest
    Chinmay Soman authored

Jul 23, 2012

  1. Peter Bailis

    Include log4j resources.dir in all tests via build.xml

    pbailis authored

Jul 11, 2012

  1. Zhongjie Wu

    Added log4j properties folder for junit test

    zhongjiewu authored

Jun 27, 2012

  1. Lei Gao

    add version and update time to client registry

    leigao authored

Jun 19, 2012

  1. Zhongjie Wu

    distinguish test report locations between normal tests and long tests

    zhongjiewu authored vinothchandar committed
  2. Zhongjie Wu

    renamed large as long to make files consistent

    zhongjiewu authored vinothchandar committed
  3. Zhongjie Wu

    Modified the test and build file to shrink the large tests.

        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
    zhongjiewu authored vinothchandar committed

Jul 14, 2011

  1. Roshan Sumbaly

    Java doc changes

    rsumbaly authored

Apr 12, 2011

  1. Roshan Sumbaly

    Adding junit-test target to build.xml - This allows you to run indivi…

    …dual unit tests as follows - ant junit-test -Dtest.name=<class_name>
    rsumbaly authored

Mar 29, 2011

  1. Roshan Sumbaly

    Revert "Add Ant tasks to measure the code coverage of the unit tests …

    …using the Cobertura"
    
    Reverting it since it pollutes the junit output
    This reverts commit c6a9034.
    rsumbaly authored

Feb 18, 2011

  1. Harold Lee

    Add Ant tasks to measure the code coverage of the unit tests using th…

    …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.
    haroldl authored afeinberg committed

Dec 27, 2010

  1. Dave Brosius

    don't include ant runtimes when compiling, which quells warnings in a…

    …nt 1.8+
    mebigfatguy authored afeinberg committed

Nov 25, 2010

  1. cleanup python client and add JSON serialization support to it

    Jonathan Traupman authored

Nov 19, 2010

  1. Alex Feinberg

    Consistent naming and indentation for ec2 targets

    afeinberg authored

Aug 06, 2010

  1. Roshan Sumbaly

    EC2 testing ant target needs to depend on 'all'

    rsumbaly authored

Aug 05, 2010

  1. Roshan Sumbaly

    Modified build.xml ec2 target to run only Smoke Tests since tests hav…

    …e their own targets
    rsumbaly authored

Jul 10, 2010

  1. jkreps

    Given that we are stuck with a number of deprecated apis we have to c…

    …all, best to supress deprecation warnings.
    jkreps authored

Jun 24, 2010

  1. Roshan Sumbaly

    Removed Krati from Contrib Unit tests since it requires more heap space

    rsumbaly authored

Dec 24, 2009

  1. Alex Feinberg

    Finished test implementations, fixed array copy "magic", added the ta…

    …rget to build.xml
    afeinberg authored

Dec 18, 2009

  1. Alex Feinberg

    Additional work on ec2 testing to work for gossip.

    afeinberg authored

Dec 04, 2009

  1. Kirk True

    Removed syspropertyset passage of properties in the ec2testing-junit …

    …Ant task. Also allowing overrides of the properties from the EC2 properties file via system properties
    kirktrue authored afeinberg committed
  2. Kirk True

    Attempting to pass logging options to the JUnit runner

    kirktrue authored afeinberg committed
  3. Kirk True

    Work to add JUnit test target for EC2, catch the error 143 exit code (h…

    …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).
    kirktrue authored afeinberg committed

Nov 29, 2009

  1. Alex Feinberg

    Modified build.xml to exclude the .git directory from the tarball.

    afeinberg authored

Nov 18, 2009

  1. bbansal

    unit test fixes.

    bbansal authored

Nov 16, 2009

  1. bbansal

    Fixed unit tests.

    bbansal authored

Nov 05, 2009

  1. bbansal

    Merge branch 'ec2-testing' of git://github.com/kirktrue/voldemort int…

    …o rebalancing
    bbansal authored

Oct 23, 2009

  1. Kirk True

    Fixed build problem.

    kirktrue authored

Oct 01, 2009

  1. Initial import of the protocol buffers based admin protocol.

    Alex Feinberg authored

Jul 10, 2009

  1. jkreps

    Add a compatibility test for json data.

    jkreps authored

Jun 29, 2009

  1. bbansal

    Fixed unresolved ${curr.release} tags in artifacts.

    bbansal authored

Jun 26, 2009

  1. bbansal

    Fixed snapshot naming issue if BUILD_NUMBER set to "".

    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.
    bbansal authored
Something went wrong with that request. Please try again.