Hi, We can also set a system property (jackrabbit.test.scale) in DailyIntegrationTest and run other tests for a longer time, for example the GCConcurrentTest, CachingHierarchyManagerTest, and maybe later some others.
Regards, Thomas On Wed, Mar 19, 2008 at 3:30 PM, Marcel Reutegger <[EMAIL PROTECTED]> wrote: > Jukka Zitting wrote: > > Currently I'm seeing about 4 minutes for "mvn -o package" and 9 > > minutes for "mvn -o install" on a clean trunk checkout on my laptop. I > > think that's a bit too much, I'd prefer to have the mvn package time > > down to 1-2 minutes (just a compile and basic unit tests) and the mvn > > install time to around 5 minutes (basic integration tests plus the > > TCK). Longer-running test cases should be delegated to a nightly CI > > build. > > > > WDYT? > > now that we have a DailyIntegrationTest test suite we could move the time > consuming tests there. I guess MultiThreadingTest is a candidate (takes 220 > seconds on my machine). > > does anyone object moving MultiThreadingTest to the daily test suite? > > regards > marcel >
