Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] tycho-gmp.gmf.tooling builds consumes enormous amount of memory

2012/2/23 Winston Prakash <winston.prakash@xxxxxxxxx>

On 2/23/12 10:29 AM, Denis Roy wrote:

The job is hogging memory -- it needs to go. 

The problem is, I can't say conclusively the memory consumption I saw is transient or permanent. It is based on one memory dump I took. I need to analyze more dumps. I got 4 so far.

I just looked at the jobs artifacts of tycho-gmp.gmf.tooling. I see a large file (145 MB)

hudsonbuild@hudson:/opt/public/jobs/tycho-gmp.gmf.tooling/builds/135> ls -la maven*.xml

-rw-r--r--  1 hudsonbuild callisto-dev 145185863 2012-02-21 13:49 maven-build-23fc8cf8-9fe3-4a66-8e73-2612c606debf.xml

I suspect it could be because the maven3 job configuration set to use "private maven repository". I'll uncheck that and do a build and see if that helps.  

I believe that many projects (maybe all ?) use private maven repository inside job workspace
for the following reasons:
  • potentially corrupting some
    p2 information needed for Tycho-based builds
  • in general build jobs run into big trouble if some artifacts in maven repository shared
    across build jobs are corrupted since build engineers can't fix this on their own since
    they don't have direct write access to this shared maven repository so they can't delete
    the corrupt artifacts. With job-local, private maven repository this can be easily fixed by
    wiping the job's workspace which will throw away the private maven repository.

Back to the top