gatk-3.8/public/java/test/org/broadinstitute/sting
Mark DePristo 39bc9e999d Add a test to LocusIteratorByState to ensure that we aren't holding reads anywhere
-- Run an iterator with 100Ks of reads, each carrying MBs of byte[] data, through LIBS, all starting at the same position.  Will crash with an out-of-memory error if we're holding reads anywhere in the system.
-- Is there a better way to test this behavior?
2013-01-14 16:30:16 -05:00
..
commandline Updated all JAVA file licenses accordingly 2013-01-10 17:06:41 -05:00
gatk Retire LegacyLocusIteratorByState 2013-01-11 15:17:18 -05:00
jna Updated all JAVA file licenses accordingly 2013-01-10 17:06:41 -05:00
utils Add a test to LocusIteratorByState to ensure that we aren't holding reads anywhere 2013-01-14 16:30:16 -05:00
AutoFormattingTimeUnitTest.java Updated all JAVA file licenses accordingly 2013-01-10 17:06:41 -05:00
BaseTest.java Updated all JAVA file licenses accordingly 2013-01-10 17:06:41 -05:00
MD5DB.java Updated all JAVA file licenses accordingly 2013-01-10 17:06:41 -05:00
MD5Mismatch.java Updated all JAVA file licenses accordingly 2013-01-10 17:06:41 -05:00
StingTextReporter.java Updated all JAVA file licenses accordingly 2013-01-10 17:06:41 -05:00
TestNGTestTransformer.java Updated all JAVA file licenses accordingly 2013-01-10 17:06:41 -05:00
WalkerTest.java Updated all JAVA file licenses accordingly 2013-01-10 17:06:41 -05:00