David Roazen 3ab78543a7 Fix tests that were consistently or intermittently failing when run in parallel on the farm ... -Make MaxRuntimeIntegrationTest more lenient by assuming that startup overhead might be as long as 120 seconds on a very slow node, rather than the original assumption of 20 seconds -In TraverseActiveRegionsUnitTest, write temp bam file to the temp directory, not to the current working directory -SimpleTimerUnitTest: This test was internally inconsistent. It asserted that a particular operation should take no more than 10 milliseconds, and then asserted again that this same operation should take no more than 100 microseconds (= 0.1 millisecond). On a slow node it could take slightly longer than 100 microseconds, however. Changed the test to assert that the operation should require no more than 10000 microseconds (= 10 milliseconds) -change global default test timeout from 20 to 40 minutes (things just take longer on the farm!) -build.xml: allow runtestonly target to work with scala test classes		2013-03-06 13:56:54 -05:00
..
net/sf	Updated all JAVA file licenses accordingly	2013-01-10 17:06:41 -05:00
org/broadinstitute/sting	Fix tests that were consistently or intermittently failing when run in parallel on the farm	2013-03-06 13:56:54 -05:00