# Fresh Source Build Fails Some Integration Tests **URL:** \ **Category:** Bugs\ **Created:** [January 25, 2016, 3:24pm UTC](https://discuss.gradle.org/t/fresh-source-build-fails-some-integration-tests/13973 "2016-01-25T15:24:17Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![eljobe](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/eljobe/32/4290_2.png) [@eljobe](https://discuss.gradle.org/u/eljobe)\ **Post date:** [January 25, 2016, 3:24pm UTC](https://discuss.gradle.org/t/fresh-source-build-fails-some-integration-tests/13973/1 "2016-01-25T15:24:17Z")
I have been struggling to get an initial clean ./gradlew build run. At first, there were just obvious problems like: 1. No JAVA\_HOME set. (Installed the latest JDK8 from Oracle’s site and set JAVA\_HOME) 2. Problems with NativeBuilds. (Installed XCode on my MacBookPro) But, now I have come to some failing integration tests which I think are actually problematic. I would have attached is a zip file containing the contents of the gradle/subprojects/launcher/build/reports/integTest directory immediately following the failed build, but new users cannot upload files. So, instead, I’ve posted them to: [http://technodabble.com/gradle/integTest.zip](http://technodabble.com/gradle/integTest.zip) The output from the command-line looks like this: :launcher:integTest Java HotSpot™ 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 org.gradle.launcher.continuous.ChangesDuringBuildContinuousIntegrationTest \> new build should be triggered when input files to tasks are changed after each task has been executed, but before the build has completed F AILED org.spockframework.runtime.SpockComparisonFailure at ChangesDuringBuildContinuousIntegrationTest.groovy:93 org.spockframework.runtime.SpockComparisonFailure at ChangesDuringBuildContinuousIntegrationTest.groovy:93 org.spockframework.runtime.SpockComparisonFailure at ChangesDuringBuildContinuousIntegrationTest.groovy:93 org.spockframework.runtime.SpockComparisonFailure at ChangesDuringBuildContinuousIntegrationTest.groovy:93 org.gradle.launcher.continuous.ChangesDuringBuildContinuousIntegrationTest \> new build should be triggered when input files to tasks are changed during the task is executing F AILED org.spockframework.runtime.SpockComparisonFailure at ChangesDuringBuildContinuousIntegrationTest.groovy:138 org.spockframework.runtime.SpockComparisonFailure at ChangesDuringBuildContinuousIntegrationTest.groovy:138 org.spockframework.runtime.SpockComparisonFailure at ChangesDuringBuildContinuousIntegrationTest.groovy:138 org.spockframework.runtime.SpockComparisonFailure at ChangesDuringBuildContinuousIntegrationTest.groovy:138 org.gradle.launcher.continuous.ContinuousBuildChangeReportingIntegrationTest \> should report the absolute file path of the first 3 chang es and report the number of other changes when more that 3 files are added to the input directory of each task F AILED org.spockframework.runtime.ConditionNotSatisfiedError at ContinuousBuildChangeReportingIntegrationTest.groovy:208 org.gradle.launcher.continuous.ContinuousBuildChangeReportingIntegrationTest \> should report the changes when files are removed FAILED org.spockframework.runtime.SpockComparisonFailure at ContinuousBuildChangeReportingIntegrationTest.groovy:204 org.spockframework.runtime.SpockComparisonFailure at ContinuousBuildChangeReportingIntegrationTest.groovy:204 org.gradle.launcher.continuous.ContinuousBuildChangeReportingIntegrationTest \> should report the changes when files are modified FAILED org.spockframework.runtime.SpockComparisonFailure at ContinuousBuildChangeReportingIntegrationTest.groovy:204 org.gradle.launcher.continuous.ContinuousBuildChangeReportingIntegrationTest \> should report the changes when directories are added FAIL ED org.spockframework.runtime.SpockComparisonFailure at ContinuousBuildChangeReportingIntegrationTest.groovy:204 org.gradle.launcher.continuous.ContinuousBuildChangeReportingIntegrationTest \> should report the changes when directories are deleted FA ILED org.spockframework.runtime.SpockComparisonFailure at ContinuousBuildChangeReportingIntegrationTest.groovy:204 org.spockframework.runtime.SpockComparisonFailure at ContinuousBuildChangeReportingIntegrationTest.groovy:204 org.gradle.launcher.continuous.ContinuousBuildChangeReportingIntegrationTest \> should report the changes when multiple changes are made at once F AILED org.spockframework.runtime.SpockComparisonFailure at ContinuousBuildChangeReportingIntegrationTest.groovy:204 org.gradle.launcher.continuous.jdk7.SymlinkContinuousIntegrationTest \> can use symlinked directory for input FAILED org.gradle.launcher.continuous.AbstractContinuousIntegrationTest$UnexpectedBuildStartedException at SymlinkContinuousIntegrationTest .groovy:94 158 tests completed, 9 failed, 18 skipped :launcher:integTest FAILED :cleanUpDaemons FAILURE: Build failed with an exception. - What went wrong: Execution failed for task ‘:launcher:integTest’. There were failing tests. See the report at: file:///Users/pepper/dev/gradle/subprojects/launcher/build/reports/integTest/index.html - Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED Total time: 25 mins 45.253 secs ---
**Author:** ![mark\_vieira](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/mark_vieira/32/5396_2.png) [@mark\_vieira](https://discuss.gradle.org/u/mark_vieira)\ **Post date:** [January 25, 2016, 9:58pm UTC](https://discuss.gradle.org/t/fresh-source-build-fails-some-integration-tests/13973/2 "2016-01-25T21:58:13Z")
Some of the continuous build integration tests are a little funky and are optimized to run in our virtualized CI environment (which introduces its own set of problems). @lhotari are there any tricks to getting these tests to pass locally? ---
**Author:** ![sterling](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/sterling/32/5395_2.png) [@sterling](https://discuss.gradle.org/u/sterling)\ **Post date:** [January 26, 2016, 7:51pm UTC](https://discuss.gradle.org/t/fresh-source-build-fails-some-integration-tests/13973/3 "2016-01-26T19:51:45Z")
Those tests are broken on OSX. We’re looking at them, but they’re safe to ignore right now. ---
**Author:** ![lhotari](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/lhotari/32/5552_2.png) [@lhotari](https://discuss.gradle.org/u/lhotari)\ **Post date:** [January 27, 2016, 10:37pm UTC](https://discuss.gradle.org/t/fresh-source-build-fails-some-integration-tests/13973/4 "2016-01-27T22:37:47Z")
The tests have been fixed on OSX in the master branch. The WatchService implementation on OSX is a polling implementation and behaves in a different way compared to Linux or Windows WatchService.