Attempting to build the gradle project fails


(aroberts) #1

Attempting to build the gradle project fails

I am attempting to build an unmodified version of the gradle source using the gradlew wrapper in the project and the build is failing with the following error.

./gradlew build

:integTest:integTest

org.gradle.integtests.ParallelProjectExecutionIntegrationTest > executes dependency project targets concurrently FAILED

org.gradle.listener.ListenerNotificationException at ParallelProjectExecutionIntegrationTest.groovy:52

Caused by: java.lang.AssertionError at ParallelProjectExecutionIntegrationTest.groovy:52

544 tests completed, 1 failed, 13 skipped :integTest:integTest FAILED

FAILURE: Build failed with an exception.

My Environment: ./gradlew -v

------------------------------------------------------------ Gradle 1.4 ------------------------------------------------------------

Gradle build time: Monday, January 28, 2013 3:42:46 AM UTC Groovy: 1.8.6 Ant: Apache Ant™ version 1.8.4 compiled on May 22 2012 Ivy: 2.2.0 JVM: 1.7.0_09 (Oracle Corporation 23.2-b09) OS: Linux 3.2.0-37-generic amd64

Ubuntu Linux 12.04 (cinnamon desktop) > uname -a Linux *** 3.2.0-37-generic #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I would like to work on contributing some improvements, but I need to be able to build the project first.


(Peter Niederwieser) #2

It happens from time to time, due to a bad commit or unstable test. You can watch the official build status at http://builds.gradle.org (see ‘Gradle - Master - Commit Builds’). You can continue the build despite a test failure with ‘–continue’.


(Peter Walker) #3

Hi Adam, Please could you supply a bit more information: Number of cores. Amount of RAM.


(aroberts) #4

dual core 4 gigs of memory

I double checked, for the changeset I am on the CI build is green on the official build (changeset id: 83db5ce227b2568894ccf49e1eb3bdb4c039da34)


(Luke Daley) #5

Hi Adam,

The error output should give you the location of the HTML test report. We’d need to see that before we could diagnose any further.


(aroberts) #6

I don’t see any way to attach the file, so I just copied the visible text into a Gist

https://gist.github.com/AdamRoberts/daf4308b0240f222550c


(alexgirao) #7

it is trivial to solve, the ParallelTaskPlanExecutor.java uses only 2 executor threads by default, and the cyclic barrier pattern of ParallelProjectExecutionIntegrationTest.groovy requires 3 concurrent threads in one of its tests, adding

executer.withArgument(’–parallel-threads=10’)

to the ‘setup’ method is sufficient to fix it, I made a gist with the patch/diff in https://gist.github.com/alexgirao/8392632


(Luke Daley) #8

I’ve fixed this. Thanks for the detective work and patch.