Just as another data point, we have modules with 1,200 functional tests (not unit tests!) that only take 45 minutes to run using Gradle. I'm sure they would take just as long using Ant. However, I'm not sure how much output is produced by these tests (other than "Success" or "Failure"), so it might be some difference like that. But, I don't think it's only because of the number of tests.
On Fri, Jan 6, 2012 at 12:25 AM, gavares <ggava...@apptio.com> wrote: > Stab in the dark: > > With so many tests, I'm wondering if the volume of output from the tests is > filling some internal buffers in the gradle daemon. Swap starts to happen > and perhaps some massive GC as well. I've been disabling tests as they > *appear* to cause the daemon spike but, no matter which test I disable, the > spike continues. > > Any ideas what else might be triggering this? We're committed to the move > from Ant to Gradle and we want to make this work. > > -- John Murph Automated Logic Research Team
