Might have been a temporal problem locally since this special test performs 
rather quick in our hudson:

https://hudson.apache.org/hudson/job/OpenJPA-trunk/370/org.apache.openjpa$openjpa-persistence-jdbc/testReport/

The locking tests of corse are really slow in hudson too.

Might be worth moving all the expensive test into an own 'integration-test' 
profile? 
Otherwise developers will just take the shortcut and don't run the whole build 
prior to a checkin because it takes so long ;)

LieGrue,
strub

--- On Thu, 1/6/11, Mark Struberg <[email protected]> wrote:

> From: Mark Struberg <[email protected]>
> Subject: Tests take forever
> To: [email protected]
> Date: Thursday, January 6, 2011, 1:56 PM
> Hi!
> 
> Anyone has an idea why some of our tests take almost
> forever when they run inside the build, but are very cheap
> if run standalone?
> 
> My build currently takes ~ 1h 15minutes on a 4x3GHz and
> also not much longer on my notebook. This indicates that
> there is something 'foul' with them. Either they wait
> unnecessarily long or they do not scale (even when built
> with mvn -T4)
> 
> An example: 
> 
> I got the following results for 
> org.apache.openjpa.lib.conf.TestEquivalentConfiguration:
>     testOldStylePersistenceUnitConfiguration
>     6.541
>     testNewStylePersistenceUnitConfiguration
>     206
>    
> testMixedStylePersistenceUnitConfiguration
>     223
>    
> testConflictStylePersistenceUnitConfiguration
>     18
>     testNewStyleSystemPropertyConfiguration
>     214
>     testOldStyleSystemPropertyConfiguration
>     223
>    
> testMixedStyleSystemPropertyConfiguration    
> 256
>    
> testConflictStyleSystemPropertyConfiguration
>     16
>     testOldStyleRuntimePropertyConfiguration
>     249
>     testNewStyleRuntimePropertyConfiguration
>     231
>    
> testMixedStyleRuntimePropertyConfiguration
>     24
>    
> testConflictStyleRuntimePropertyConfiguration
>     18
> 
> makes 844 seconds in summary.
> 
> But the same test passes in 4.034 seconds when I run this
> test in Idea (all 12 tests pass).
> 
> I used the following VM settings:
> -Dopenjpa.Log=DefaultLevel=INFO
> -Dopenjpa.DynamicEnhancementAgent=false
> -Dopenjpa.ConnectionDriverName=org.apache.derby.jdbc.EmbeddedDriver
> -Dopenjpa.ConnectionURL=jdbc:derby:target/database/openjpa-derby-database;create=true
> -Dopenjpa.ConnectionUserName= -Dopenjpa.ConnectionPassword=
> 
> Is there anything I miss? 
> 
> Looks like we should pretty easily be able to slash down
> our build to 20 minutes or so...
> 
> 
> LieGrue,
> strub
> 
> 
>       
> 



Reply via email to