| Re: [platform-releng-dev] [eclipse-build]Build M20060919-1045 (Timestamp: 200609191045):Automated JUnit testing complete. Test failures/errors occurred. |
Didn't the test pass in R3.2 with the same VM? Maybe we introduced a leak.
Dani
Mike Wilson
<Mike_Wilson@ca.i
bm.com> To
Sent by: "Eclipse platform release
platform-releng-d engineering list."
ev-bounces@eclips <platform-releng-dev@xxxxxxxxxxx>
e.org cc
Subject
20.09.2006 17:55 Re: [platform-releng-dev]
[eclipse-build]Build
M20060919-1045 (Timestamp:
Please respond to 200609191045):Automated JUnit
"Eclipse platform testing complete. Test
release failures/errors occurred.
engineering
list."
<platform-releng-
dev@xxxxxxxxxxx>
If the test is known to fail, because of a VM limitation, can we just
exclude it for 3.2.x testing?
McQ.
Kim
Moir/Ottawa/IBM@
IBMCA To
Sent by: pwebster@xxxxxxxxxxxxxxxxxxx, "Eclipse platform
platform-releng- release engineering list."
dev-bounces@ecli <platform-releng-dev@xxxxxxxxxxx>
pse.org cc
Subject
09/20/06 11:40 Re: [platform-releng-dev] [eclipse-build]Build
M20060919-1045 (Timestamp:
200609191045):Automated JUnit testing
Please respond complete. Test failures/errors occurred.
to
"Eclipse
platform
release
engineering
list."
I enquired about this issue during today's arch call. We won't be changing
the version of the 1.5 reference vm for Linux in as listed in the 3.2
plan.
http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html
So this test failure will remain in subsequent 3_2 maintenance builds.
Kim
"Paul Webster"
<paulweb515@xxxxxxxxx>
Sent by:
platform-releng-dev-bou To
nces@xxxxxxxxxxx "Eclipse platform release engineering
list." <platform-releng-dev@xxxxxxxxxxx>
cc
09/20/2006 10:51 AM
Subject
Re: [platform-releng-dev]
Please respond to [eclipse-build]Build M20060919-1045
pwebster@alumni.uwater (Timestamp: 200609191045):Automated JUnit
loo.ca; Please respond testing complete. Test
to failures/errors occurred.
"Eclipse platform
release engineering
list."
<platform-releng-dev@e
clipse.org>
On 9/20/06, Kim Moir <Kim_Moir@xxxxxxxxxx> wrote:
I reran the ui tests and the same failure occured again.
Kim
It looks like that test is failing with a OutOfMemoryError:
[java] ----- testActionSets
[java] testActionSets: setUp...
[java] testActionSets: tearDown...
[java] !ENTRY org.eclipse.jdt.core 4 4 2006-09-19 14:47:06.052
[java] !MESSAGE Background Indexer Crash Recovery
[java] !STACK 0
[java] java.lang.OutOfMemoryError: Java heap space
[java] Exception in thread "Java indexing" java.lang.OutOfMemoryError:
Java heap space
[java] ----- testActionSetPartAssociations
[java] testActionSetPartAssociations: setUp...
[java] testActionSetPartAssociations: tearDown...
These tests are running on 1.5.0_06, which has a known permgen size
problem.
We can't replicate the errors on jdk 1.5.0_07 on linux. I don't believe
this effects the quality of the build.
We're tracking failures in the same set of tests in the I builds using
https://bugs.eclipse.org/bugs/show_bug.cgi?id=157978
--
Paul Webster
But I neeeeed tacos! I need them or I will explode!
That happens to me sometimes! - GIR
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev