I forgot that there is already an enhancement request on this
intermittent OOME in bug# 291410
If I increase the heap from 512 to 2048 (for 64 bit JVM's only with
over 4GB ram) I no longer crash running the ant report - it generates
We will need a user assignable build property in the future for
this to accomidate either 32 or 64 bit JVM's.
Michael O'Brien wrote:
The trunk JPA LRG ant script is not reporting on all the tests after
a change between rev# 562x - 564x.
I have tested this on 2 different views.
Run the JPA LRG using the following target instead the new default -
then we get a report on the full JPA LRG - giving us all JPA results
and not just on the last antcall target run.
[junit] Tests run: 1531, Failures: 0, Errors: 0, Time elapsed:
Note: However there is a discrepancy between tests in ant = 1531 and
eclipse = 1644
Modify the generate-report target to report on multiple antcall targets
>For the last 3-5 days the JPA LRG ant run has had different
behavior - it reports on only a subset of 75 of the total 1644 tests.
Running the JPA LRG from Eclipse in the testing browser is fine.
I suspect that some change to build.xml in the trunk or
jpa/eclipselink.jpa.test directory has caused this.
It looks like the following target is being run
<!-- Runs LRG (FullRegressionTestSuite) with agent. -->
<target name="test-lrg" depends="clean-test, config-trunk,
instead of this one which reports on all 1644 tests
<!-- Default test target, run the LRG -->
<target name="test" depends="clean-test, config-trunk,
VERSION: Eclipse Persistence Services - 2.0.0.qualifier
TEST MODEL NAME: JPA Tests
RESULTS OF TEST MODEL: JPA Tests
Fatal Errors: 0
Setup Warnings: 0
Setup Failures: 0
Total Time: 1535486
Total Tests: 1644
I get the following XML test output after a refresh from 3-5 days ago
Name Status Type Time(s)
testUpdateEmployee Error Forked Java VM exited abnormally. Please note
the time in the report does not reflect the time until the VM exit.
Error: Forked Java VM exited abnormally. Please note the time in the
report does not reflect the time until the VM exit.
Q)Has any one else had recent issues with the ant JPA test run?
eclipselink-dev mailing list