On 02/05/2011, at 12:10 AM, Spencer Allain wrote: > org.gradle.integtests.CommandLineIntegrationTest FAILED > org.gradle.integtests.CrossVersionCompatibilityIntegrationTest FAILED > > Using the latest source from git yesterday I successfully compiled > everything, but running the developerBuild task took a _really_ long time and > never completed (hung after 503 tests), but that's probably because I > attempted to run it under Windows 7.
The dev build on windows is currently broken, and will hang. We will fix this soon. We do want people to be able to use windows to work on gradle. But, given that none of the gradle developers use windows, the reality is that it doesn't always work as well as it could. We have a CI build that runs on windows, so things don't stay broken too long. > > Before it stopped responding, though, two tests failed. > > As for the canDefineJavaHomeViaEnvironmentVariable failure, the exception is > as follows (not sure why path redefinition didn't stick, maybe because the > test environment itself gets forked somewhere?): > > java.lang.RuntimeException: Gradle execution failed in > C:\play\gradle\subprojects\integ-test\build\tmp\tests\CommandLineIntegrationTest\canDefineJavaHomeViaEnvironmentVariable > with: cmd [/c, gradle, -PexpectedJavaHome=C:\Java\jdk1.6.0_21, > --gradle-user-home, C:\play\gradle\intTestHomeDir\worker-32, checkJavaHome] > Output: > :checkJavaHome > > * What went wrong: > Execution failed for task ':checkJavaHome'. > Cause: Assertion failed: > > assert Jvm.current().javaHome == file(expectedJavaHome) > | | | | | > | | | | C:\Java\jdk1.6.0_21 > | | | C:\Java\jdk1.6.0_21 > | | false > | C:\Program Files\Java\jre6 > 1.6.0_21 (Sun Microsystems Inc. 17.0-b17) Do you have a stack trace for this failure, so we can see where in the test method it failed? The test runs Gradle a few times. > > > As for the wrapper issue: > > java.lang.RuntimeException: Could not build test project using Gradle 0.9.1 > What went wrong: > A problem occurred evaluating root project > 'canUseWrapperFromPreviousVersionToRunCurrentVersion'. > Cause: Unexpected Gradle version '1.0-milestone-4-20110430125113-0400' Gradle 0.9.1 had a bug in it where the Wrapper task type couldn't handle a negative timezone offset in the Gradle version. And so, this test will fail when your timezone is behind GMT. I'll fix this test so it skips this particular combination. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
