Hello!
Good to know it also works outside my laptop!
It could be beneficial to find out which test cases benefit from specifying
Derby timeout. I suspect we have a few. One is TestException but this is
intentional. There might be others which deadlock and we do not want this. The
way to find them seems to monitor CPU and disk activity when the test suite is
running. I remember seeing periods when CPU and disk were zero.
I could look into this but chances are that only when week-end come. What about
a JIRA on this, so we remember?
Cheers,
Milosz
> +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
>
> > +1, as you said, if not affecting any tests.
> >
> > On Sat, Mar 28, 2009 at 8:15 AM, Miłosz Tylenda 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:
> > >
> > >
> > >
> > > openjpa.Log
> > >
> > DefaultLevel=${openjpa.loglevel}
> > >
> > >
> > > openjpa.ConnectionDriverName
> > >
> > > org.apache.commons.dbcp.BasicDataSource
> > >
> > >
> > > derby.stream.error.file
> > > target/derby.log
> > >
> > >
> > > derby.locks.waitTimeout
> > > 5
> > >
> > >
> > > openjpa.ConnectionProperties
> > > DriverClassName=${
> > connection.driver.name
> > >
> > },Url=${connection.url},Username=${connection.username},Password=${connection.password},${dbcp.args}
> > >
> > >
> > >
> > > We could consider setting this permanently. Hope it will not affect
> > > timeout-related tests.
> > >
> > > Greetings,
> > > Milosz
> > >
> > >
> >
> >
> > --
> > Albert Lee.
> >
>
