search

gosu-lang / gradle-gosu-plugin

BSD 3-Clause "New" or "Revised" License
5 stars 7 forks source link

Upgrade to Gradle 2.9 #16

Closed DPUkyle closed 8 years ago

DPUkyle commented 8 years ago

At first glance, there are two issues with TestKit which make this non-trivial:

  1. GradleRunner's API changed, removing getStandardOutput and getStandardError methods
  2. In initial testing, withDebug(true) did not work for debugging functional tests
DPUkyle commented 8 years ago

I made a forum post re: item 2 above: https://discuss.gradle.org/t/2-9-gradlerunner-withdebug-true-does-not-halt-execution/12852

DPUkyle commented 8 years ago

Marked wontfix - although I refactored all tests in branch gradle-gosu-plugin/gradle2.9, the TestKit/GradleRunner does not give us enough control over daemons\ - I cannot find a way to turn them off, and the excessive amount of daemons spawned will cause an OOME exception on our CI server. We may have to wait until a future version of Gradle with better memory and daemon management in the TestKit API is released.

\ From https://docs.gradle.org/current/userguide/test_kit.html:

51.2.2. Controlling the build environment

The runner executes the test builds in an isolated environment by specifying a dedicated "working directory" in a directory inside the JVM's temp directory (i.e. the location specified by the java.io.tmpdir system property, typically /tmp). _Any configuration in the default Gradle user home directory (e.g. ~/.gradle/gradle.properties) is not used for test execution. The TestKit does not expose a mechanism for fine grained control of environment variables etc._ Future versions of the TestKit will provide improved configuration options.