Provide more insights about "Multiple Gradle daemons were used".

Sometimes when I run benchmarks/profiling it fails with

* Stopping daemons
java.lang.RuntimeException: Multiple Gradle daemons were used.
	at org.gradle.profiler.Main.checkPid(Main.java:461)
	at org.gradle.profiler.Main.runGradleScenario(Main.java:188)
	at org.gradle.profiler.Main.run(Main.java:80)
	at org.gradle.profiler.Main.main(Main.java:27)

But nowhere in stdout/stderr or profile.log can I find logs that indicate when and why Gradle daemon was started.

What’s more weird is that I’m getting that in very isolated environment: a Docker container gets started for every profile/benchmark session.

(But I’ve also seen it in non-containerized runs).

Would be great if gradle-profiler could give more info about it, ideally it should be actionable 😃

[ZacSweers]

We just gave up on trying to work around this and believe that Gradle’s GC polling is currently flawed. We disable GC polling instead via setting the org.gradle.daemon.gc.polling.disabled system property to true and have been fine since.

[kenyee]

I don’t see anything in the checkpid code that would be affected by that flag though: https://github.com/gradle/gradle-profiler/blob/df9ede45b5e4d21822b3bcbb38b58ef66d3deb05/src/main/java/org/gradle/profiler/GradleScenarioInvoker.java

Looks like a fairly simple pid comparison of gradle daemons…no way to opt out in that code…