Re: [wtp-releng] RE: [wtp-dev] Ongoing JUnit failures in 3.0.4 builds
The default is already -Xmx758m (I picked that value, since I that's our
usual recommendation for realistic "production work" (meaning, it'd be
rare for us to _require_ more than that).
The VM we use on the build machine doesn't use "maxPermSize".
(It is an IBM VM, for PPC architecture).
Are you using a Java 6 VM for your local testing?
We recently changed to use a Java 6 VM to run the tests on the build
Does your test lib, myfaces-core-1.1.5 work with Java 6? Or should that be
Any other changes that would cause an increase in memory?
I'd hate to see this "fixed" just by increasing our already large memory
allocation, but if you run out of ideas, we can try 1028m
Debajit Adhikary <DEBAJIT.ADHIKARY@xxxxxxxxxx>
12/16/2008 05:32 PM
[wtp-releng] RE: [wtp-dev] Ongoing JUnit failures in 3.0.4 builds
This is with reference to the failing pagedesigner JUnits in the 3.0.4
builds. (The pagedesigner tests throw an OutOfMemoryError)
I ran the JUnits locally with the VM args:
and the failing tests ran successfully.
The same tests, however, failed locally when no such VM settings were
Is there any way to increase the memory made available to the tests on the
From: Nitin Dahyabhai [mailto:nitind@xxxxxxxxxx]
Sent: Monday, December 15, 2008 11:00 AM
Subject: [wtp-dev] Ongoing JUnit failures in 3.0.4 builds
Although I've cleared up the JSDT versioning related failures in our 3.0.4
builds, the build is still consistently breaking
I'm not sure what's going on with the WebServices Axis-related test, but
the JSF Page Designer tests appear to either not be finishing or running
out of memory:
. Is there something that needs to change when running the Page Designer
tests? And is the WebServices failure being looked at?
Eclipse WTP Source Editing
wtp-dev mailing list
wtp-releng mailing list