Current Behavior
Today, the Gradle TestKit sets the daemon idle timeout to 3 minutes which in terms of a CI-based build is quite a long time.
Expected Behavior
It would be nice if there was a way to allow user configuration of that timeout through the TestKit public API, so that the idle timeout can be set to a lower value if desired.
Context
Whether this is the way that it should be done or not is up for debate, but... in our environment we have a couple of Gradle plugins that we want utilize automated testing to ensure functional compatibility across Gradle versions. In order to achieve this, we are utilizing Spockframework for writing the functional test and then utilizing TestKit to open up Gradle daemon's for each of the Gradle versions under test. Because the default timeout is set to 3 minutes when utilizing TestKit, we are getting into a bind of not having enough memory on our CI server's agents to go around for these tests and the other executions going on. As an aside, I know that nebula-plugins/nebula-test supports a memory safe mode -- where they set the timeout to 15 seconds, but it's still not fully user configurable -- so I could utilize that, but the purpose of this issue is rather to see this addition of functionality adopted by Gradle core.
Current Behavior
Today, the Gradle TestKit sets the daemon idle timeout to 3 minutes which in terms of a CI-based build is quite a long time.
Expected Behavior
It would be nice if there was a way to allow user configuration of that timeout through the TestKit public API, so that the idle timeout can be set to a lower value if desired.
Context
Whether this is the way that it should be done or not is up for debate, but... in our environment we have a couple of Gradle plugins that we want utilize automated testing to ensure functional compatibility across Gradle versions. In order to achieve this, we are utilizing Spockframework for writing the functional test and then utilizing TestKit to open up Gradle daemon's for each of the Gradle versions under test. Because the default timeout is set to 3 minutes when utilizing TestKit, we are getting into a bind of not having enough memory on our CI server's agents to go around for these tests and the other executions going on. As an aside, I know that nebula-plugins/nebula-test supports a memory safe mode -- where they set the timeout to 15 seconds, but it's still not fully user configurable -- so I could utilize that, but the purpose of this issue is rather to see this addition of functionality adopted by Gradle core.