Hi Jukka, > I wonder if this has something to do with the current > capacity problems we've been seeing on the > Hudson master.
A resource problem is very likely. The test runs of OpenCMIS are very expensive and I had to adapt MAVEN_OPTS several times because of OutOfMemory error occurs. Current settings are: -Xms256m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m In detail OpenCMIS testing is starting a Jetty server which runs the InMemory repository. Then OpenCMIS runtime junit tests executing through the whole OpenCMIS stack: client runtime, provider layer, network binding until each test case hits finally the jetty server. All of this is quite effortful but ensures a high code quality. Hopefully this is not too expensive to run on Apache Hudson landscape. Regards, Stephan -----Original Message----- From: Jukka Zitting [mailto:[email protected]] Sent: Dienstag, 23. März 2010 12:16 To: [email protected] Subject: Re: OpenCMIS Hudson updates Hi, On Thu, Mar 18, 2010 at 6:23 PM, Klevenz, Stephan <[email protected]> wrote: > I'm also analyzing these build problems (timeout, etc.) but until now with no > success. Sometimes the build hangs and repeating the build without code > change between works or vice versa. I run a Hudson build locally and in > parallel > that does not show these kind of problems (except real build errors). There seems to again be a build stuck. I wonder if this has something to do with the current capacity problems we've been seeing on the Hudson master. For now I've tied the OpenCMIS build to the two Ubuntu build slaves, which should avoid problems caused by load on the Hudson master. Let's see whether that helps. > I suggest to change back to mailing list notifications after the reason is > found > and build is more stable. Agreed. BR, Jukka Zitting
