I am looking into deadlock. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott M Stark > Sent: Tuesday, January 20, 2004 11:34 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] Automated JBoss(Branch_3_2 > WonderLand) Testsuite Results: 18-January-2004 > > Out of these failures, the following need to be resolved before the > 3.2.4RC1 release: > > Suite: org.jboss.test.cts.test.StatefulSessionUnitTestCase > Test: testStrictPooling > > Suite: org.jboss.test.jmx.test.DeployXMBeanUnitTestCase > Test: testUserXMBeanPersistentValues > > Suite: org.jboss.test.security.test.EJBSpecUnitTestCase > Test: testMDBRunAs > > Suite: org.jboss.test.deadlock.test.BeanStressTestCase > Test: testDeadLock > > Suite: org.jboss.test.deadlock.test.BeanStressTestCase > Test: testAllCompleteOrFail > > Suite: org.jboss.test.deadlock.test.BeanStressTestCase > Test: testAllCompleteOrFailNotSupportedReentrant > > Suite: org.jboss.test.deadlock.test.BeanStressTestCase > Test: testAllCompleteOrFailCMR > > Suite: > org.jboss.test.jca.test.CachedConnectionBankStressTestCase > Test: testCachedConnectionBank > > Suite: org.jboss.test.lock.test.EnterpriseEntityStressTestCase > Test: unknown > > > The remainder are known issues. I'm working on the > DeployXMBeanUnitTestCase and EJBSpecUnitTestCase failures. I > need to know who is looking into the others. > > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
