Running gradle 1.8 under Hudson for a CI installation, the build is failing at variable points with a Kyro buffer underflow exception.
The stack trace is here: https://gist.github.com/anonymous/6886334.
From previous postings, this seems to be caused by a worker process exiting with a non-zero exit status (137)
I’m trying to debug it, and have a suspicion the worker is running out of memory. I’ve tried changing the JVM parameters with a -D switch, but it does not seem to affect it. So:
is there any way to see more diagnostic info from the worker? I don’t see any way to get memory info, exception/error stacks from the worker - what is the preferred way to give more memory to the worker processes? Since I can’t monitor them, I don’t know if I am giving gradle the right switches to do that.
The problem does not happen when running from the command line - can you suggest anything in the CI environment that might be affecting this.
All help much appreciated!