On Fri, Nov 27, 2009 at 1:27 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:

>
> Also one thing I'd love to try is NOT forking the JVM for each test
> (fork="no" in the junit task).  I wonder how much time that'd buy...
>
>
it shaves off a good deal of time on my machine.

'ant test-core': 4 minutes, 39 seconds -> 3 minutes, 3 seconds
'ant test':  11 minutes, 8 seconds -> 7 minutes, 13 seconds

however, it makes me a little nervous because i'm not sure all the tests
cleanup nicely if they change statics and stuff.
anyway, here's the trivial patch (you don't want fork=no, because it turns
off assertions)

Index: common-build.xml
===================================================================
--- common-build.xml    (revision 909395)
+++ common-build.xml    (working copy)
@@ -398,7 +398,7 @@
            </condition>
                <mkdir dir="@{junit.output.dir}"/>
            <junit printsummary="off" haltonfailure="no" maxmemory="512M"
-             errorProperty="tests.failed" failureProperty="tests.failed">
+             errorProperty="tests.failed" failureProperty="tests.failed"
forkmode="perBatch">
              <classpath refid="@{junit.classpath}"/>
              <assertions>
                <enable package="org.apache.lucene"/>

-- 
Robert Muir
rcm...@gmail.com

Reply via email to