Re: [wtp-releng] RE: [wtp-dev] Ongoing JUnit failures in 3.0.4 builds

[David M Williams <david_williams@xxxxxxxxxx>]

> We recently changed to use a Java 6 VM to run the tests on the build 
> machine. 

Well my apologies! After looking closely at your logs for this failing 
test, I see I did NOT switch to Java 6! 
I missed a spot that had to be changed and never followed through to check 
closely. 

I thought that went too smoothly. I'll switch to Java 6 on 3.0.4 
maintenance (first) as I don't want to 
cause churn for getting M4 done on Friday. (Though, if anyone wants me to 
switch before M4, just say the word). 

Thanks, 





From:
David M Williams/Raleigh/IBM@IBMUS
To:
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
Date:
12/16/2008 06:40 PM
Subject:
Re: [wtp-releng] RE: [wtp-dev] Ongoing JUnit failures in 3.0.4 builds
Sent by:
wtp-releng-bounces@xxxxxxxxxxx



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 
machine. 

Does your test lib, myfaces-core-1.1.5 work with Java 6? Or should that be 

updated? 

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

Thanks, 








From:
Debajit  Adhikary <DEBAJIT.ADHIKARY@xxxxxxxxxx>
To:
wtp-releng@xxxxxxxxxxx
Date:
12/16/2008 05:32 PM
Subject:
[wtp-releng] RE: [wtp-dev] Ongoing JUnit failures in 3.0.4 builds
Sent by:
wtp-releng-bounces@xxxxxxxxxxx



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:
-Xmx512M -XX:MaxPermSize=512M
and the failing tests ran successfully.

The same tests, however, failed locally when no such VM settings were 
specified.

Is there any way to increase the memory made available to the tests on the 

build machine? 

- Debajit



-----Original Message-----
From: Nitin Dahyabhai [mailto:nitind@xxxxxxxxxx]
Sent: Monday, December 15, 2008 11:00 AM
To: wtp-dev@xxxxxxxxxxx
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: 
http://build.eclipse.org/webtools/committers/wtp-R3.0-M/20081211111933/M-3.0.4-20081211111933/testResults/html/org.eclipse.jst.pagedesigner.tests.AllTests.html 


.  Is there something that needs to change when running the Page Designer 
tests?  And is the WebServices failure being looked at?

Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational

_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng



_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng