Hi Lewis, I made a commit this morning to the trunk (r1495698) which triggered Jenkins build #984. When I saw the build failure I thought "uh oh... have I just broken something?" but the changes from the previous build were tiny (CHANGES.txt and a couple of Javadoc edits in the DataDeliveryServlet class, no code changes). I had a quick look through the console output for the build and saw the following (you've probably already seen this before posting your email):
Java HotSpot(TM) Server VM warning: Insufficient space for shared memory file: /tmp/hsperfdata_jenkins/29391 Try using the -Djava.io.tmpdir= option to select an alternate temp location. I'm not sure if this was a one-off glitch or whether it also caused some of the other build failures. Ross On 22 Jun 2013, at 17:11, Lewis John Mcgibbney <[email protected]> wrote: > Good Morning, > The intermittent test can be attributed to memory allocation on whichever > slave we build oodt trunk on. > I am not really comfortable with the fact that the buulds fails like > this... > I will try my best to look in to this... regards less if it means assigning > more mem to the builfd? > Any thoughts? All works good for me every day and I do svn up every day > Have a great weekend troops > Lewis > > -- > *Lewis*
