And there's the log here:
http://bamboo.ci.codehaus.org/build/viewBuildLog.action?buildNumber=81&buildKey=GROOVY-GROOVY160J14On Tue, Jun 30, 2009 at 20:39, Roshan Dawrani<
roshandawrani@...> wrote:
> If you look at the web page:
http://bamboo.ci.codehaus.org/browse/GROOVY,
> you will see that the last build entry, pointing to
>
http://bamboo.ci.codehaus.org/browse/GROOVY-GROOVY160J14, indicates the
> build failure mentioned in the email.
>
>
> On Wed, Jul 1, 2009 at 12:04 AM, Hamlet D'Arcy <
hamletdrc@...> wrote:
>>
>> Hi gang,
>>
>> I got an email from the CI server that said my changes broke the build:
>>
>> [Bamboo] GROOVY - Trunk - JDK 1.6 - Uber build (Coverage,
>> Documentation, Examples) build 81 has FAILED (0 tests failed). Change
>> made by hamletdrc
>> BUILD FAILED
>>
>> /opt/j2ee/domains/ci.codehaus.org/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-2.1.4/xml-data/build-dir/GROOVY-GROOVY160J14/build.xml:274:
>> Forked groovyc returned error code: 1
>>
>> But the Bamboo website is showing the build passing:
>>
>>
http://bamboo.ci.codehaus.org/build/viewBuildHistory!default.action?buildKey=GROOVY-CORE>>
>> Is the build failing or not?
>>
>> --
>> Hamlet D'Arcy
>>
hamletdrc@...
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>
http://xircles.codehaus.org/manage_email>>
>>
>
>
--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email