Set forkEvery=1 for stability improvement of embulk-standards tests

Question

To improve embulk-standards tests stability, this PR changes configuration of Gradle test processes with forkEvery=1. It recreates Gradle test processes every test class execution and expect reduction of the heap memory consumption. As the result, it might make the test faster. https://docs.gradle.org/3.2.1/dsl/org.gradle.api.tasks.testing.Test.html

forkEvery=1

$ ./gradlew :embulk-standards:test
Publication bintrayMavenRelease not found in project :.
Publication bintrayMavenRelease not found in project :embulk-cli.
Publication bintrayMavenRelease not found in project :embulk-docs.
:embulk-jruby-strptime:compileJava UP-TO-DATE
:embulk-jruby-strptime:processResources UP-TO-DATE
:embulk-jruby-strptime:classes UP-TO-DATE
:embulk-jruby-strptime:jar UP-TO-DATE
:embulk-core:compileJava UP-TO-DATE
:embulk-core:unpackGems UP-TO-DATE
:embulk-core:processResources UP-TO-DATE
:embulk-core:classes UP-TO-DATE
:embulk-core:jar UP-TO-DATE
:embulk-core:compileTestJava UP-TO-DATE
:embulk-core:processTestResources UP-TO-DATE
:embulk-core:testClasses UP-TO-DATE
:embulk-standards:compileJava UP-TO-DATE
:embulk-standards:processResources UP-TO-DATE
:embulk-standards:classes UP-TO-DATE
:embulk-test:compileJava UP-TO-DATE
:embulk-test:processResources UP-TO-DATE
:embulk-test:classes UP-TO-DATE
:embulk-test:jar UP-TO-DATE
:embulk-standards:compileTestJava UP-TO-DATE
:embulk-standards:processTestResources UP-TO-DATE
:embulk-standards:testClasses UP-TO-DATE
:embulk-standards:test

BUILD SUCCESSFUL

Total time: 5 mins 43.545 secs

forkEvery=0 (not set)

$ ./gradlew :embulk-standards:test
Publication bintrayMavenRelease not found in project :.
Publication bintrayMavenRelease not found in project :embulk-cli.
Publication bintrayMavenRelease not found in project :embulk-docs.
:embulk-jruby-strptime:compileJava UP-TO-DATE
:embulk-jruby-strptime:processResources UP-TO-DATE
:embulk-jruby-strptime:classes UP-TO-DATE
:embulk-jruby-strptime:jar UP-TO-DATE
:embulk-core:compileJava UP-TO-DATE
:embulk-core:unpackGems UP-TO-DATE
:embulk-core:processResources UP-TO-DATE
:embulk-core:classes UP-TO-DATE
:embulk-core:jar UP-TO-DATE
:embulk-core:compileTestJava UP-TO-DATE
:embulk-core:processTestResources UP-TO-DATE
:embulk-core:testClasses UP-TO-DATE
:embulk-standards:compileJava UP-TO-DATE
:embulk-standards:processResources UP-TO-DATE
:embulk-standards:classes UP-TO-DATE
:embulk-test:compileJava UP-TO-DATE
:embulk-test:processResources UP-TO-DATE
:embulk-test:classes UP-TO-DATE
:embulk-test:jar UP-TO-DATE
:embulk-standards:compileTestJava UP-TO-DATE
:embulk-standards:processTestResources UP-TO-DATE
:embulk-standards:testClasses UP-TO-DATE
:embulk-standards:test

BUILD SUCCESSFUL

Total time: 34 mins 16.844 secs

该提问来源于开源项目：embulk/embulk

Answer 1

It seems that it enables reducing wait time for CI passed actually.

10 mins 45 secs: https://ci.appveyor.com/project/embulk/embulk/build/set_forkevery_for_testing%20345 11 mins 22 secs: https://ci.appveyor.com/project/embulk/embulk/build/master%20350 10 mins 9 secs: https://travis-ci.org/embulk/embulk/builds/251372666 11 mins 18 secs: https://travis-ci.org/embulk/embulk/builds/251370130