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
