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. -- View this message in context: http://gradle.1045684.n5.nabble.com/Gradle-daemon-160-CPU-usage-during-long-test-run-tp5124315p5124650.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
