Jump to: navigation, search

Common Build Infrastructure/Testing/VMArgs

< Common Build Infrastructure‎ | Testing
Revision as of 16:37, 1 February 2010 by Nickboldt.gmail.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Warning2.png
Draft Content
This page is currently under construction. Community members are encouraged to maintain the page, and make sure the information is accurate.


Depending on your hardware, the default settings for the Eclipse Test Framework, as outlined in org.eclipse.test/library.xml, may be insufficient to run your tests without and OutOfMemory error or permgen crash.

Below are some settings you can define in your testing.properties file:

  • To use a different library-file than the default from org.eclipse.test/library.xml
library-file=${relengCommonBuilderDir}/builder/tests/custom-library.xml

or

library-file=${relengBuilderDir}/my-own-library.xml
  • To dump test properties into console log and separate file for debugging purposes
echotestproperties=true
  • Set some -X flags
Xflags= -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m
  • Increase the default osgi.bundlefile.limit (see bug 106396)
Dflags=-Dosgi.bundlefile.limit=100
  • If Xflags or Dflags have been overridden, must override args too
args=${executionDir}/${shell} -vmExecutable ${vmExecutable} -consolelog ${consolelog} ${Xflags} ${Dflags}