|Re: [cross-project-issues-dev] tycho-gmp.gmf.tooling builds consumes enormous amount of memory|
Exactly what does keeping JUnit test results in memory mean?
HiExactly what does keeping JUnit test results in memory mean? For the MDT/OCL JUnit tests, the derived TestCase classes have fields that can reference useful and sometimes large models. These used to be a major source of 'leakage' and sometimes prevented tests running in 512M. After making sure that all fields were nulled in tearDown() they run in 32M. GMF Tooling uses MDT/OCL, so they may be encountering a similar form of model lock-in.
After the build is done, Hudson keeps some of the build artifacts such as JUNit or maven metadata info. Since hudson keeps all the builds of all joba, this bloats up the memory. The immediate solution is reduce the foot print of these build artifacts, if we can. Long term term solution is fix Hudson not to keep all the builds in memory
cross-project-issues-dev mailing list
tel: 06 75 09 19 88
Mia-Software, 410 clos de la Courtine
.: model driven agility :.
Back to the top