Re: is 51,000 tests too much in a job?

> Check how much heap you have allowed jenkins to use. We're currently running with -XX:PermSize=128M -XX:MaxPermSize=512M -Xmx16384M and the jenkins memory graph under /monitoring shows us maxing out under 12GB, and that seems excessive to me, since we only have about a dozen builds go

is 51,000 tests too much in a job?

Is 51,000 tests too much in a single job? We're seeing painful slowdowns in the Jenkins UI and this question came up. Our junit.xml file is about 17MB in size. Are other people running that number of tests successfully? -- You received this message because you are subscribed to the Google

jenkins UI hanging on job page, threads blocked

For one one our builds, if we try to load a job page like /job/www/12345/, the browser would hang forever and the jenkins /monitoring page would show the thread blocked on TestResultAction Handling GET /job/www/43365/ from x.x.x.x : RequestHandlerThread[#17] AbstractBuild/index.jelly A

web UI hangs as app reads all old junitResult..xml files

The first time we click on a link to see a build, the web UI hangs for about ten minutes. stracing the thread that's got 100% of the cpu shows that it's reading each one of the 500 junitResult.xml files: ... open("/var/lib/jenkins/jobs/www/builds/42596/junitResult.xml", O_RDONLY) = 382 open("/

Re: stale jenkins campfire plugin is 2.1, github latest is 2.5

On Sat, Dec 1, 2012 at 1:41 PM, Christopher Orr wrote: > > I did a release, as version 2.6. It should appear in the Jenkins Update > Centre soon-ish. > > FTW! Thanks. -- Kevin M. Goess Software Engineer Berkeley Electronic Press kgo...@bepress.com 510-665-1200 x179 www.bepress.com bepress: