Interestingly, there seems to be a big difference between mvn clean install -> 8.5 minutes and mvn test -> 5.5 - 6 minutes
So when just running "mvn test" we get the "fast" build time (which works out about right if the new deadlock test takes 10-20 secs). What is the difference between mvn clean install and mvn test? I doubt that compiling takes 2-3 minutes, especially because previously mvn clean install took 5-6 minutes. Could it be that the maven-failsafe-plugin redundantly runs some tests (performance tests) that are also executed in the surefire test run? So basically the performance tests are run twice? On Thu, May 22, 2014 at 1:18 AM, Ralph Goers <[email protected]>wrote: > I added a test that checks for a deadlock. I recall it taking about 10-20 > seconds on my machine. I tried to make it be as fast as it could be and > still catch the deadlock when it occurred. > > Ralph > > On May 21, 2014, at 8:42 AM, Remko Popma <[email protected]> wrote: > > > What happened with the build? > > I brought it down from 8 minutes to 5.5 minutes on my PC > > and now it is 8.5 minutes again! One step forward, two steps back... > > > > Is this because the maven-failsafe-plugin tests were added? If so, can > we take that out? > > > > Or set it up so that the performance tests are only run during > continuous integration. I thought that's why the performance tests were > separated out, or did I misunderstand? > > > > Remko > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
