+1. Tested on 1.0.x and it dropped the time for mvn clean test from nearly 10 minutes to just over 2.
I'll give it a try on other branches when I get a chance, but this looks great to me. Thanks for finding it Milosz! -mike 2009/3/28 Albert Lee <[email protected]> > +1, as you said, if not affecting any tests. > > On Sat, Mar 28, 2009 at 8:15 AM, Miłosz Tylenda <[email protected]> wrote: > > > Hi All! > > > > Have anybody experimented with setting default Derby timeout in our test > > suite? I have set the timeout to 5 seconds and the test suite execution > time > > felt down from 34 to 19 minutes on my system. Part of my > > openjpa-persistence-jdbc pom.xml looks like this: > > > > <systemProperties> > > <property> > > <name>openjpa.Log</name> > > > <value>DefaultLevel=${openjpa.loglevel}</value> > > </property> > > <property> > > <name>openjpa.ConnectionDriverName</name> > > > > <value>org.apache.commons.dbcp.BasicDataSource</value> > > </property> > > <property> > > <name>derby.stream.error.file</name> > > <value>target/derby.log</value> > > </property> > > <property> > > <name>derby.locks.waitTimeout</name> > > <value>5</value> > > </property> > > <property> > > <name>openjpa.ConnectionProperties</name> > > <value>DriverClassName=${ > connection.driver.name > > > },Url=${connection.url},Username=${connection.username},Password=${connection.password},${dbcp.args}</value> > > </property> > > </systemProperties> > > > > We could consider setting this permanently. Hope it will not affect > > timeout-related tests. > > > > Greetings, > > Milosz > > > > > > > -- > Albert Lee. >
