Problem with Gradle on CI

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem with Gradle on CI

Guillaume Laforge
Hi guys,

The Groovy project is using Codehaus' Bamboo to build its sources.
And perhaps because of some disk issue (but I don't know more yet for now), the Groovy builds are failing with the following message:

28-Jan-2013 01:44:14FAILURE: Build failed with an exception.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* What went wrong:
28-Jan-2013 01:44:14Could not read cache value from '/home/j2ee-bamboo/.gradle/daemon/1.0-rc-3/registry.bin'.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* Try:
28-Jan-2013 01:44:14Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Is this something you've ever encountered?
Any remedy you might think of?

Since it appears to be an old Gradle version, I'm gonna suggest the Codehaus admin to install a more recent one.
Hopefully that'll help.

--
Guillaume Laforge
Groovy Project Manager
SpringSource, a division of VMware

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Gradle on CI

Luke Daley-3


On 28/01/2013, at 7:56, Guillaume Laforge <[hidden email]> wrote:

Hi guys,

The Groovy project is using Codehaus' Bamboo to build its sources.
And perhaps because of some disk issue (but I don't know more yet for now), the Groovy builds are failing with the following message:

28-Jan-2013 01:44:14FAILURE: Build failed with an exception.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* What went wrong:
28-Jan-2013 01:44:14Could not read cache value from '/home/j2ee-bamboo/.gradle/daemon/1.0-rc-3/registry.bin'.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* Try:
28-Jan-2013 01:44:14Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Is this something you've ever encountered?
Any remedy you might think of?

Hard to say without seeing the full exception trace.


Since it appears to be an old Gradle version, I'm gonna suggest the Codehaus admin to install a more recent one.
Hopefully that'll help.

Any reason you aren't using the wrapper?


--
Guillaume Laforge
Groovy Project Manager
SpringSource, a division of VMware

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Gradle on CI

Guillaume Laforge

On Mon, Jan 28, 2013 at 10:59 AM, Luke Daley <[hidden email]> wrote:

On 28/01/2013, at 7:56, Guillaume Laforge <[hidden email]> wrote:

Hi guys,

The Groovy project is using Codehaus' Bamboo to build its sources.
And perhaps because of some disk issue (but I don't know more yet for now), the Groovy builds are failing with the following message:

28-Jan-2013 01:44:14FAILURE: Build failed with an exception.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* What went wrong:
28-Jan-2013 01:44:14Could not read cache value from '/home/j2ee-bamboo/.gradle/daemon/1.0-rc-3/registry.bin'.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* Try:
28-Jan-2013 01:44:14Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Is this something you've ever encountered?
Any remedy you might think of?

Hard to say without seeing the full exception trace.

Unfortunately that's all I had.

Somehow, the registry.bin file was zero-length for some reason (probably some disk space issue Ben told me).
By nuking it, the builds started working again.

It might be interesting to add some checks perhaps at the Gradle level in case some needed files like that registry.bin file are not corrupt or something.
 
Since it appears to be an old Gradle version, I'm gonna suggest the Codehaus admin to install a more recent one.
Hopefully that'll help.

Any reason you aren't using the wrapper?

No good reason not to.
We'll definitely have to adapt our builds to use the wrapper. 

--
Guillaume Laforge
Groovy Project Manager
SpringSource, a division of VMware

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Gradle on CI

Ken Sipe
In reply to this post by Guillaume Laforge
Guillaume,

Are you getting this with gradlew?

Sent from my iPhone

On Jan 28, 2013, at 1:56 AM, Guillaume Laforge <[hidden email]> wrote:

Hi guys,

The Groovy project is using Codehaus' Bamboo to build its sources.
And perhaps because of some disk issue (but I don't know more yet for now), the Groovy builds are failing with the following message:

28-Jan-2013 01:44:14FAILURE: Build failed with an exception.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* What went wrong:
28-Jan-2013 01:44:14Could not read cache value from '/home/j2ee-bamboo/.gradle/daemon/1.0-rc-3/registry.bin'.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* Try:
28-Jan-2013 01:44:14Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Is this something you've ever encountered?
Any remedy you might think of?

Since it appears to be an old Gradle version, I'm gonna suggest the Codehaus admin to install a more recent one.
Hopefully that'll help.

--
Guillaume Laforge
Groovy Project Manager
SpringSource, a division of VMware

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Gradle on CI

Guillaume Laforge
Hi Ken!

No, this was with an installed Gradle.
But I don't really have control of that at Codehaus.
But I can certainly try to configure a shell to run ./gradlew instead.
Which is the right thing to do anyway.
Although the underlying problem might have been present with gradlew as well, no idea.

Guillaume



On Mon, Jan 28, 2013 at 1:34 PM, Ken Sipe <[hidden email]> wrote:
Guillaume,

Are you getting this with gradlew?

Sent from my iPhone

On Jan 28, 2013, at 1:56 AM, Guillaume Laforge <[hidden email]> wrote:

Hi guys,

The Groovy project is using Codehaus' Bamboo to build its sources.
And perhaps because of some disk issue (but I don't know more yet for now), the Groovy builds are failing with the following message:

28-Jan-2013 01:44:14FAILURE: Build failed with an exception.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* What went wrong:
28-Jan-2013 01:44:14Could not read cache value from '/home/j2ee-bamboo/.gradle/daemon/1.0-rc-3/registry.bin'.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* Try:
28-Jan-2013 01:44:14Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Is this something you've ever encountered?
Any remedy you might think of?

Since it appears to be an old Gradle version, I'm gonna suggest the Codehaus admin to install a more recent one.
Hopefully that'll help.

--
Guillaume Laforge
Groovy Project Manager
SpringSource, a division of VMware




--
Guillaume Laforge
Groovy Project Manager
SpringSource, a division of VMware

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Gradle on CI

Ken Sipe


Sent from my iPhone

On Jan 28, 2013, at 6:39 AM, Guillaume Laforge <[hidden email]> wrote:

Hi Ken!

No, this was with an installed Gradle.
But I don't really have control of that at Codehaus.
But I can certainly try to configure a shell to run ./gradlew instead.
Which is the right thing to do anyway.
Although the underlying problem might have been present with gradlew as well, no idea.

Yes... That's part of what I was trying to understand as well. Gradlew is advertised as if it worked once it always works.. Which is the way we want it:). Let me know if you need any help on moving towards it as well... I should have time this week. 

Guillaume



On Mon, Jan 28, 2013 at 1:34 PM, Ken Sipe <[hidden email]> wrote:
Guillaume,

Are you getting this with gradlew?

Sent from my iPhone

On Jan 28, 2013, at 1:56 AM, Guillaume Laforge <[hidden email]> wrote:

Hi guys,

The Groovy project is using Codehaus' Bamboo to build its sources.
And perhaps because of some disk issue (but I don't know more yet for now), the Groovy builds are failing with the following message:

28-Jan-2013 01:44:14FAILURE: Build failed with an exception.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* What went wrong:
28-Jan-2013 01:44:14Could not read cache value from '/home/j2ee-bamboo/.gradle/daemon/1.0-rc-3/registry.bin'.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* Try:
28-Jan-2013 01:44:14Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Is this something you've ever encountered?
Any remedy you might think of?

Since it appears to be an old Gradle version, I'm gonna suggest the Codehaus admin to install a more recent one.
Hopefully that'll help.

--
Guillaume Laforge
Groovy Project Manager
SpringSource, a division of VMware




--
Guillaume Laforge
Groovy Project Manager
SpringSource, a division of VMware

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Gradle on CI

Guillaume Laforge

On Mon, Jan 28, 2013 at 1:44 PM, Ken Sipe <[hidden email]> wrote:
[...]
Hi Ken!

No, this was with an installed Gradle.
But I don't really have control of that at Codehaus.
But I can certainly try to configure a shell to run ./gradlew instead.
Which is the right thing to do anyway.
Although the underlying problem might have been present with gradlew as well, no idea.

Yes... That's part of what I was trying to understand as well. Gradlew is advertised as if it worked once it always works.. Which is the way we want it:). Let me know if you need any help on moving towards it as well... I should have time this week. 

Thank you, Ken.
Well, the Groovy project is already using the wrapper, so there's nothing particular to do in this area, I think.
So it's more on the Bamboo configuration side of things that I need to look up and see how I can update all our build plans to use ./gradlew instead of the Gradle artifactory plugin for building.


--
Guillaume Laforge
Groovy Project Manager
SpringSource, a division of VMware

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Gradle on CI

Adam Murdoch
In reply to this post by Guillaume Laforge

On 28/01/2013, at 9:05 PM, Guillaume Laforge wrote:


On Mon, Jan 28, 2013 at 10:59 AM, Luke Daley <[hidden email]> wrote:

On 28/01/2013, at 7:56, Guillaume Laforge <[hidden email]> wrote:

Hi guys,

The Groovy project is using Codehaus' Bamboo to build its sources.
And perhaps because of some disk issue (but I don't know more yet for now), the Groovy builds are failing with the following message:

28-Jan-2013 01:44:14FAILURE: Build failed with an exception.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* What went wrong:
28-Jan-2013 01:44:14Could not read cache value from '/home/j2ee-bamboo/.gradle/daemon/1.0-rc-3/registry.bin'.
28-Jan-2013 01:44:14
28-Jan-2013 01:44:14* Try:
28-Jan-2013 01:44:14Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Is this something you've ever encountered?
Any remedy you might think of?

Hard to say without seeing the full exception trace.

Unfortunately that's all I had.

Somehow, the registry.bin file was zero-length for some reason (probably some disk space issue Ben told me).
By nuking it, the builds started working again.

It might be interesting to add some checks perhaps at the Gradle level in case some needed files like that registry.bin file are not corrupt or something.

Definitely. We started doing this some time around the 1.2 or 1.3 release (I can't remember exactly which one), plus a bunch of other stability fixes in this area.


--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Gradle on CI

Guillaume Laforge
On Fri, Feb 1, 2013 at 12:38 AM, Adam Murdoch <[hidden email]> wrote:
[...]

It might be interesting to add some checks perhaps at the Gradle level in case some needed files like that registry.bin file are not corrupt or something.

Definitely. We started doing this some time around the 1.2 or 1.3 release (I can't remember exactly which one), plus a bunch of other stability fixes in this area.

Thanks for the heads-up, Adam. 


--
Guillaume Laforge
Groovy Project Manager
SpringSource, a division of VMware