Gradle deamon in not killed after test execution

[ghost]

Hi,

I validate my plugin against various range of Gradle versions (from 2.0 up to 2.5) and after text executions all Gradle daemons are alive (they are 5. for now but number is growing along with new gradle releases). It would be very nice to have an option to kill Gradle daemons after forked test execution.

[szpak]

I've come across that issue implementing #23. Then (October 2014) it was not implemented on the Tooling API side. I cannot found a ticket for it, so I propose you to ask about that using their forum and drag it out of the shadows.

[ghost]

Thanks, I ask on the forum.

[ghost]

Hi, forum thread is here : https://discuss.gradle.org/t/nebula-test-and-gradle-daemon-still-alive-after-test-execution/10682
in short : it seems that from Gradle 2.6 there will be test kit, which should provide some option to control it.

But there is still a case for all older gradle versions (up to 2.5)

[szpak]

Thanks @gglab-ps for coming back with that. If you're really desperate (e.g. your CI server crashes with out of memory) you could try to kill Gradle daemon with given version number at a OS level.