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 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Sunday, January 18, 2004 12:50 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004 Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004 JBoss daily test results SUMMARY Number of tests run: 1639 -------------------------------------------- Successful tests: 1620 Errors: 9 Failures: 10 -------------------------------------------- [time of test: 2004-01-18.20-08 GMT] [java.version: 1.4.2_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_03-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-9smp] Useful resources: - http://jboss.sourceforge.net//junit-results/32/2004-01-18.20-08 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! ------------------------------------------------------- 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
