Hi Ross, No hassle at all, thanks for chiming in on this one. Looks like these are failures on the build slaves. We only save 10 builds, I'm going to increase that to 20 so we've got more of a chance of comparing intermittent failures. Thanks Lewis
On Sat, Jun 22, 2013 at 3:59 PM, Ross Laidlaw <[email protected]>wrote: > p.s. Apologies for the formatting in my previous message (sent it from my > phone) > > > > Begin forwarded message: > > *From:* Ross Laidlaw <[email protected]> > *Date:* 22 June 2013 18:42:06 BST > *To:* "[email protected]" <[email protected]> > *Subject:* *Re: intermittent tests* > > 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* > -- *Lewis*
