[jboss-dev] Help needed resolve the regression

[Adrian Brock]

On Fri, 2009-02-06 at 10:18 -0600, Brian Stansberry wrote:
> I'll figure out why the classloader leak test is failing.
> 

I've already fixed it. 
https://jira.jboss.org/jira/browse/JBCL-85

It's some new code I did for Kabir.

If you can get hudson to download the latest jboss-cl snapshot
version 4 from here:
http://snapshots.jboss.org/maven2/org/jboss/cl/jboss-classloading/2.0.3-SNAPSHOT/

Then the test passes.

> Shelly McGowan wrote:
> > Dimitris,
> > 
> > 
> > Most of the tests that are failing in the Hudson runs are passing with one-test (see below).
> > 
> > 
> > Nothing conclusive yet but I suspect a memory/classloader leak which is seen in the classloader leak tests even running individually.  Also the JBoss-AS-5.0.x-compatibilityMatrix job is failing with:
> > 
> > Error Message
> > 
> > Unexpected Error java.lang.OutOfMemoryError: GC overhead limit exceeded
> > 
> > 
> > 
> > Shelly
> > 
> > 
> > 
> > /*
> >  **Local test results with one-test.
> > */
> > 
> > [junit] Running org.jboss.test.jmx.test.JMXInvokerUnitTestCase
> > [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 20.819 sec
> > 
> > [junit] Running org.jboss.test.naming.test.InternalNamingClassReplacementUnitTestCase
> > [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 7.659 sec
> > 
> > [junit] Running org.jboss.test.web.test.WebIntegrationUnitTestCase
> > [junit] Tests run: 37, Failures: 0, Errors: 0, Time elapsed: 16.999 sec
> > 
> > [junit] Running org.jboss.test.refs.test.RefResolutionUnitTestCase
> > [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.049 sec
> > 
> > [junit] Running org.jboss.test.timer.test.SecureTimerUnitTestCase
> > [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 54.267 sec
> > 
> > 
> > [junit] Running org.jboss.test.asynch.AsynchTestCase
> > [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 4.342 sec
> > 
> > 
> > 
> > ----- Original Message -----
> > From: "Shelly McGowan" <smcgowan at redhat.com>
> > To: dimitris at redhat.com, "JBoss.org development list" <jboss-development at lists.jboss.org>
> > Sent: Friday, February 6, 2009 7:13:08 AM GMT -05:00 US/Canada Eastern
> > Subject: Re: [jboss-dev] Help needed resolve the regression
> > 
> > 
> > 
> > Dimitris,
> > 
> > I'll take a look at what's going on.
> > 
> > 
> > Shelly
> > 
> > 
> > ----- Original Message -----
> > From: "Dimitris Andreadis" <dandread at redhat.com>
> > To: "JBoss.org development list" <jboss-development at lists.jboss.org>
> > Sent: Friday, February 6, 2009 6:48:10 AM GMT -05:00 US/Canada Eastern
> > Subject: Re: [jboss-dev] Help needed resolve the regression
> > 
> > Nobody?
> > 
> > http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-testSuite-sun15/1266/testReport/
> > 
> > Dimitris Andreadis wrote:
> >> While Ales is fighting the VFS beast for the 5.0.1 release we need help 
> >> to qualify and resolve the testsuite and tck regression.
> >>
> >> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-testSuite-sun15/lastBuild/testReport/ 
> >>
> >>
> >> The majority of the failures seem to be deployment/classloader related.
> >>
> >> Thanks!
> >> /D
> >> _______________________________________________
> >> jboss-development mailing list
> >> jboss-development at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jboss-development
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> 
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx